On Fri, Dec 09, 2005 at 09:05:28PM +0100, Laurent Bonnaud wrote:
> > First of all, this is wrong; do not put /usr/lib/debug/usr/lib in the
> > library path. GDB loads libraries from /usr/lib/debug/{lib/,usr/lib/}
> > automatically. They contain debug information, but no symbols.
>
> Thank you fo
> This was a bug in GDB; I will fix it in the next upload. You can work
> around it using "handle SIG33 pass nostop noprint", for now.
Thank you for the workaround, I would not guessed it myself :>. It
works for me.
> > 1. With debug libraries:
> >
> > $ export LD_LIBRARY_PATH=/usr/lib/debug:/
> I can't reproduce either of these using gdb 6.3.90.20051119-1. Please
> let me know if you still can;
No, cases #1 and #3 from my initial report now work, and crash #2 can be
avoided thanks to your workaround (handle SIG33 pass nostop noprint).
I'm looking forward to the next gdb upload ! Th
On Wed, Dec 07, 2005 at 10:19:23PM -0500, Daniel Jacobowitz wrote:
> > 1. With debug libraries:
> >
> > $ export LD_LIBRARY_PATH=/usr/lib/debug:/usr/lib/debug/usr/lib
>
> > [Thread 147466 (LWP 20325) exited]
> > Cannot get thread event message: generic error
> > (gdb)
>
> First of all, this is w
On Tue, Aug 23, 2005 at 03:42:51PM +0200, Laurent Bonnaud wrote:
> I'm trying to debug numerous galeon crashes I'm experiencing nowadays.
>
> I tried 3 different debug settings and each time gdb did not launch galeon
> successfully and output different error messages.
Sorry for the delay. There'
Package: gdb
Version: 6.3-6
Severity: important
Hi,
I'm trying to debug numerous galeon crashes I'm experiencing nowadays.
I tried 3 different debug settings and each time gdb did not launch galeon
successfully and output different error messages.
1. With debug libraries:
$ export LD_LIBRARY_
6 matches
Mail list logo
