Re: Thread debugging cause unknow signal ? with gdb 4.18 and libc6

ak (ak@ebox.de)
Fri, 03 Sep 1999 18:52:19 +0200

Messages sorted by: [ date ][ thread ][ subject ][ author ]
Next message: Andrea Arcangeli: "Re: CONFIG_BIGMEM and rawio"
Previous message: Mark Hahn: "Re: /proc/cpuinfo verbiage differ unnecessarily between ports..."

> it is inpossible to me debug (gdb 4.18) my thread application that base on
> linuxthreads (libpthread from libc6 2.1.2-0pre7). gdb does not recognize
> thread creation (pthread_create) and receive unknown signal :-( The gdb output
> is the following:
> Pgoram received signal ?, Unknown signal.
> 0x4004814a in sigsuspend() from /lib/libc.so.6

I ran into the same situation today after successfully debugging
threads for quiet a while.

I used to debug with gdb 4.17.0.11 from Suse 6.1. When I updated to
Suse 6.2, which has gdb 4.18, it gave the same problems you are
mentioning. So, I downgraded back to 4.17 and it's ok now again.

Alex

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

Next message: Andrea Arcangeli: "Re: CONFIG_BIGMEM and rawio"
Previous message: Mark Hahn: "Re: /proc/cpuinfo verbiage differ unnecessarily between ports..."