This is the mail archive of the cygwin@cygwin.com mailing list for the Cygwin project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
I noticed that in.rlogind.exe coredumps (latest inetutils, with both 1.5.5. and cvs), both on NT and on 9X/ME. It happens after bash exits (so that it isn't immediately obviously), in the cleanup () routine if (logout(p)) logwtmp(p, "", ""); with logwtmp() calling _logwtmp(), which updates wtmp and crashes on return (?). The attached file contains the dump and the interesting part of the trace. I don't have the time to fully pursue this. Here are two other unrelated observations: 1) The cygwin logout() updates wtmp, but all the applications I have checked (ssd, telnetd,..) also do it (as shown above), so that there will be two logout records. I am not sure if logout() is expected to update wtmp: <http://www.freebsd.org/cgi/man.cgi?query=logout&apropos=0&sektion=3&manpath =FreeBSD+5.1-RELEASE&format=html> 2) in ftruncate64 (), the syscall_printf should print "length" as a long long. Pierre
Attachment:
trace.txt
Description: Text document
-- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |