On Thu, Jun 30, 2005 at 03:37:25PM +0100, Dave Korn wrote: > I think I remember noticing that backtracing across sigfe doesn't always >work too well. Then again, there could be a problem with the debug info:
"doesn't always" == "never". >>#3 0x00435d27 in fhandler_pipe::get_guard () > >makes no sense. But I would imagine the peculiarity is down to sigfe; >it does something unexpected to the stack frame, that the debug info >doesn't reflect. No, it's due to the fact that 0x00435d27 is an address in the application and the application has no debugging symbols. >>In case you haven't noticed, I'm running a snapshot, which, IIUC, *is* >>a debug build. And that doesn't help much, as you can see. > >Debug yes; unoptimised, I think not, although we'd need cgf or cv to >confirm how the snapshot process works. The snapshots are unstripped. Otherwise, it is a normal build. cgf -- 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/
