Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Alan Hourihane <alan_hourihane@hotmail.com>
Cc: gdb@sources.redhat.com
Subject: Re: multithreaded app debugging
Date: Thu, 24 Apr 2003 13:54:00 -0000	[thread overview]
Message-ID: <20030424135409.GA13765@nevyn.them.org> (raw)
In-Reply-To: <b88lo0$hbj$1@main.gmane.org>

On Thu, Apr 24, 2003 at 01:37:45PM +0100, Alan Hourihane wrote:
> Hi,
> 
> I'm debugging a threaded application, but somewhere within the second
> thread it gets a
> 
> Program received signal SIG32, Real-time event 32
> 
> And then I hit continue for gdb to splurt out...
> 
> Couldn't get registers: Operation not permitted.
> 
> Any clues on how to fix gdb for this. I'm not sure where the SIG32 signal
> is coming from either.

That means the multithread code was not enabled; usually this means GDB
had a problem loading or activating thread_db, or got the wrong copy of
libpthread.so, or something similar.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


      reply	other threads:[~2003-04-24 13:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-24 12:41 Alan Hourihane
2003-04-24 13:54 ` Daniel Jacobowitz [this message]

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=20030424135409.GA13765@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=alan_hourihane@hotmail.com \
    --cc=gdb@sources.redhat.com \
    /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