GCC untrackable crashes

Thu Feb 22 05:48:00 GMT 2001

Christopher Faylor wrote:
>> On Wed, Feb 21, 2001 at 06:43:40PM -0800, Kevin Camera wrote:
> >Thanks for the tip. In fact, the debugger was in thread 1, and the only
> >other thread did not offer any other information. So unfortunately the
> >problem was with the compiler or debugger, since all threads had no trace
> >information.
>> Hmm. As someone who uses the compiler and debugger on an almost daily basis
> I have to say that I have never seen this behavior on a program that was
> compiled with debugging info (-g).
>
Well, I can't say that I use GDB that often but everytime that I've used
it I see this problem. I've been able to switch to the assembler
listing and set breakpoints on each instruction of the object containing
main() and be able to get a source code point of problem.
YMMV,
Earnie.
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple