On Fri, Jan 16, 2004 at 11:16:03PM -0500, Pierre A. Humblet wrote: >At 10:49 PM 1/16/2004 -0500, Christopher Faylor wrote: >>On Fri, Jan 16, 2004 at 09:21:35PM -0500, Pierre A. Humblet wrote: >>>On Fri, Jan 16, 2004 at 04:52:59PM -0500, Christopher Faylor wrote: >>>>Did my latest cvs checkin fix this? It seems to for me but I don't >>>>have time for extensive testing. >>> >>>It does, but when I uncomment the setsid() in the program and run from >>>command.com, sh -c ./a.exe stays in the foreground (no prompt) when >>>CYGWIN=notty. Things are OK with CYGWIN=tty. >> >>A fix to fhandler_console::close seems to rectify this behavior. >>Strange that it worked ok on XP. > >As I was rebuilding I got JIT gdb to kick in for gcc thread 1 (and then >make). It's possible that it's due to something weird in my previous >build from cvs in my sandbox. I should really try with a snapshot >(tomorrow)
Sorry but this stack trace is obvious nonsense. It's not even worth posting something this garbled. Surely you know this. cgf >CYGWIN_ME-4.90 hpn5170x 1.5.6(0.108/3/2) 2004-01-16 20:54 i686 unknown >unknown Cygwin > >#0 0xbff66879 in KERNEL32!CallNamedPipeW () >#1 0xbff64257 in MultiByteToWideChar () >#2 0xbff641cf in MultiByteToWideChar () >#3 0xbffbb490 in TlsFree () >#4 0xbff7f9fd in KERNEL32!EnumSystemCodePagesA () >#5 0xbffbb490 in TlsFree () >#6 0x838bccec in ?? () >#7 0x61028213 in ret_here () > at ../../../../src/winsup/cygwin/exceptions.cc:406 >#8 0xbff66821 in KERNEL32!CallNamedPipeW () >#9 0x0074e8c8 in ?? () >#10 0x0074ede0 in ?? () >#11 0x0074e8e4 in ?? () >#12 0x0074e8a0 in ?? () >#13 0x0074ede0 in ?? () >#14 0xbff6682d in KERNEL32!CallNamedPipeW () >#15 0x0074ede0 in ?? () >#16 0x0074e8b0 in ?? () >#17 0xbff7845a in KERNEL32!BuildCommDCBA () >#18 0x0074e8c8 in ?? () >#19 0x0074ede0 in ?? () >#20 0x0074e8e4 in ?? () >#21 0x0074e8a0 in ?? () >#22 0x61027d60 in ZZ17handle_exceptionsE19__PRETTY_FUNCTION__ () -- 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/
