* Problems with GDB 5.1 and Pthreads
@ 2001-12-13 8:50 Marcos Pindado Sebastián
2001-12-13 8:56 ` Daniel Jacobowitz
2001-12-13 12:20 ` Michael Snyder
0 siblings, 2 replies; 3+ messages in thread
From: Marcos Pindado Sebastián @ 2001-12-13 8:50 UTC (permalink / raw)
To: gdb-patches
[-- Attachment #1: Type: text/plain, Size: 901 bytes --]
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.
[-- Attachment #2: Type: text/html, Size: 1710 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Problems with GDB 5.1 and Pthreads
2001-12-13 8:50 Problems with GDB 5.1 and Pthreads Marcos Pindado Sebastián
@ 2001-12-13 8:56 ` Daniel Jacobowitz
2001-12-13 12:20 ` Michael Snyder
1 sibling, 0 replies; 3+ messages in thread
From: Daniel Jacobowitz @ 2001-12-13 8:56 UTC (permalink / raw)
To: Marcos Pindado Sebastián; +Cc: gdb-patches
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Problems with GDB 5.1 and Pthreads
2001-12-13 8:50 Problems with GDB 5.1 and Pthreads Marcos Pindado Sebastián
2001-12-13 8:56 ` Daniel Jacobowitz
@ 2001-12-13 12:20 ` Michael Snyder
1 sibling, 0 replies; 3+ messages in thread
From: Michael Snyder @ 2001-12-13 12:20 UTC (permalink / raw)
To: Marcos Pindado Sebastián; +Cc: gdb-patches
> 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.
This is typical of a mismatch between gdb and glibc.
Newer versions of gdb use a newer version of glibc to
interface to the pthread library.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2001-12-13 20:20 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-12-13 8:50 Problems with GDB 5.1 and Pthreads Marcos Pindado Sebastián
2001-12-13 8:56 ` Daniel Jacobowitz
2001-12-13 12:20 ` Michael Snyder
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox