Re: debug information

2006-06-15 Thread Wynfield Henman
Brian, thanks for the lead and helpfull information regarding SIGSEGV. Henman On 6/2/06, Brian Dessent <[EMAIL PROTECTED]> ... Please search the archives for the many recent threads on this topic. What you are seeing is not an actual SIGSEGV, it is a bug/limitation in gdb related to how Cygw

Re: debug information

2006-06-01 Thread Brian Dessent
Wynfield Henman wrote: > If anyone would give me a lead as to how to get a more meaningful > backtrace from gdb, I would appreciate it. Please search the archives for the many recent threads on this topic. What you are seeing is not an actual SIGSEGV, it is a bug/limitation in gdb related to how

debug information

2006-05-31 Thread Wynfield Henman
If anyone would give me a lead as to how to get a more meaningful backtrace from gdb, I would appreciate it. I was wandering if I have to build a new cygwin.dll (using cygwin) with symbol information or it that is even possible. cygwin version 5.19.4 Thanks

How to get dos path's in the debug information?

2002-01-28 Thread Mack Lobell
Hi, we just received a 2.95.3 cross compiler, host is cygwin (NT 4.0, SP6) and target is powerpc. The problem we have is that the target elf has cygwin path's (/cygdrive/c/some path/file.c) instead of dos path's (c:\some path\file.c). Our debuggers can't find the source files unless they get t