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's three different problems here. Out of
order:
> 2. Without LD_LIBRARY_PATH (stange thread IDs !):
That's standard for NPTL.
> Program received signal SIG33, Real-time event 33.
> [Switching to Thread -1224819792 (LWP 20331)]
> 0xffffe410 in __kernel_vsyscall ()
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.
> 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 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.
I don't have a 32-bit galeon available right now to try LinuxThreads.
I'll fix that and give this a try.
> 3. Without NTPL:
>
> $ LD_ASSUME_KERNEL=2.4.22 gdb /usr/bin/galeon
> [...]
> (gdb) run
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 81926 (LWP 20629)]
> 0xb7f00f4b in strlen () from /lib/ld-linux.so.2
Ditto.
--
Daniel Jacobowitz
CodeSourcery, LLC
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
