Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: "Marcos Pindado Sebastián" <mpindado@signalia.es>
Cc: gdb-patches@sources.redhat.com
Subject: Re: Problems with GDB 5.1 and Pthreads
Date: Thu, 13 Dec 2001 08:56:00 -0000	[thread overview]
Message-ID: <20011213115442.A18313@nevyn.them.org> (raw)
In-Reply-To: <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


  reply	other threads:[~2001-12-13 16:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-13  8:50 Marcos Pindado Sebastián
2001-12-13  8:56 ` Daniel Jacobowitz [this message]
2001-12-13 12:20 ` Michael Snyder

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20011213115442.A18313@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=mpindado@signalia.es \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox