This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: Problems with GDB 5.1 and Pthreads
- From: Daniel Jacobowitz <drow at mvista dot com>
- To: Marcos Pindado Sebastián <mpindado at signalia dot es>
- Cc: gdb-patches at sources dot redhat dot com
- Date: Thu, 13 Dec 2001 11:54:42 -0500
- Subject: Re: Problems with GDB 5.1 and Pthreads
- References: <004b01c183f6$e63a52e0$050c010a@sigsirius>
Probably you do not have libthread_db installed. Glibc may not be new
enough.
On Thu, Dec 13, 2001 at 05:54:57PM +0100, Marcos Pindado Sebastián wrote:
> Hi.
> I am developing under linux SlackWare 7.0 and have several problems with gdb and multithreaded programs.
> Gdb is 5.1 configured on P3 PC.
> - Every call to a pthread function results in the reception of a SIG32. I have tried to resolve this by ignoring that signal, but...
> - It does not appear any message indicating a new thread is created.
> - I don't see any thread when writing : info threads.
> - The command " thread x" does not work, it says it has no id thread.
> - When I set a breakpoint in the code that a thread other than main thread the program does not stop in it, but recives a SIGTRAP when that thread exists.
>
> It seems there is no thread over there although simple multithread programs work fine (when not debugging) so I am assuming Slackware does well with threads.
> Is there any configuration option I have miss? Is there any patch to resolve this?
>
> Thank you very much.
>
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer