Mail Archives: cygwin/2009/10/01/10:35:37
On Thu, Oct 01, 2009 at 01:50:31PM +0100, Fergus wrote:
>Strange. I know you are not very interested in debugging user-specific
>bespoke executables and I know that providing a test case would be
>ideal, but an executable that has built and executed here successfully
>under Cygwin [1.5] for the last nn years, fails in [1.7] with the message
>
>$ ./this_is_the_user_executable.exe
>assertion "root_idx != -1" failed: file
>"/netrel/src/cygwin-1.7.0-61/winsup/cygwin/mount.cc", line 363,
>function: void mount_info::init()
>Stack trace:
>Frame Function Args
>00229974 7713F003 (0000003C, 0000EA60, 00000000, 00229A98)
>00229988 7713EFB2 (0000003C, 0000EA60, 000000A4, 00229A7C)
>00229A98 610B9E93 (00000000, 0000003C, 00229AB8, 00000000)
>00229B78 610B6B27 (00000000, 00000000, 00000000, 00000000)
>00229BC8 610B6F3B (00000348, 00229BF0, 00229C04, 00229C04)
>00229C88 610B7061 (00000348, 00000006, 00229CB8, 610B7105)
>00229C98 610B709C (00000006, 0022CE88, 00229CB8, C98AA326)
>00229CB8 610B7105 (6115A054, 61191E44, 61191E54, 0000016B)
>00229CE8 6100109B (61191E54, 0000016B, 611922AC, 61191E44)
>0022CD18 6107B57D (60FD000C, 611D4798, 004E1E68, 6106E0E9)
>0022CD78 610B2090 (00000000, 0022CDB0, 610066F0, 7FFDF000)
>End of stack trace
>
>Crazy I know, but is there anything obviously wrong (or recently
>changed) with mount.cc at your end? I'm using Windows 7 build 7600.
>Thank you.
Wouldn't cygcheck output be a pretty obviously helpful thing to provide
here?
Heck, since we're talking about the mount table, even that would have
been a bare minimum.
cgf
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
- Raw text -