This is the mail archive of the gdb@sources.redhat.com mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: gdb stack trace shows only those frames after the signal

From: Joel Brobecker <brobecker at gnat dot com>
To: srikrish <srikrish at in dot ibm dot com>
Cc: gdb at sources dot redhat dot com
Date: Wed, 24 Dec 2003 08:03:20 +0100
Subject: Re: gdb stack trace shows only those frames after the signal
References: <00c701c3c965$424c6a90$fd0eb609@srikrishnan> <00e501c3c966$3fc1ab90$fd0eb609@srikrishnan>

> After handling a signal the previous stack trace is lost. Is this a
> known problem? Any fixes?

Try GDB 6.0, or GDB from CVS. The symptoms are identical to a problem
that I have seen before which were fixed in GDB 6.0.

-- 
Joel

Follow-Ups:
- Re: gdb stack trace shows only those frames after the signal
  - From: srikrish

References:
- gdb stack trace shows only those frames after the signal
  - From: srikrish
- Re: gdb stack trace shows only those frames after the signal
  - From: srikrish

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]