Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
To: drow@false.org
Cc: gdb@sourceware.org
Subject: Re: generic error with a statically linked multithreaded program
Date: Thu, 19 Apr 2007 09:19:00 -0000	[thread overview]
Message-ID: <20070419.181940.21590034.nemoto@toshiba-tops.co.jp> (raw)
In-Reply-To: <20070406.183844.05598302.nemoto@toshiba-tops.co.jp>

On Fri, 06 Apr 2007 18:38:44 +0900 (JST), Atsushi Nemoto <anemo@mba.ocn.ne.jp> wrote:
> > > Is it http://sources.redhat.com/bugzilla/show_bug.cgi?id=2696, right?
> > > 
> > > If so, the gdb patch mentioned in it is already merged in gdb 6.6?
> > 
> > I think so, but I don't remember for sure.
> 
> I tried the libc patch on MIPS and it works fine with gdbserver.
> 
> But with MIPS native gdb, I got a little bit different error message:
> thread_get_info_callback: cannot get thread info: generic error
> 
> Do you have any thoughts on this error?
...
> thread_get_info_callback: cannot get thread info: generic error

I have tracked down this error and I found that your last patch titled
"RFC: Handle early debugging in NPTL applications"
(http://sourceware.org/ml/gdb-patches/2006-02/msg00496.html) is not
merged yet.  With this patch applied, I can debug NPTL static program
with native gdb.

---
Atsushi Nemoto


      reply	other threads:[~2007-04-19  9:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-05  5:58 Atsushi Nemoto
2007-04-05 10:51 ` Atsushi Nemoto
2007-04-05 14:29 ` Daniel Jacobowitz
2007-04-05 14:39   ` Atsushi Nemoto
2007-04-05 14:45     ` Daniel Jacobowitz
2007-04-06  9:40       ` Atsushi Nemoto
2007-04-19  9:19         ` Atsushi Nemoto [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=20070419.181940.21590034.nemoto@toshiba-tops.co.jp \
    --to=anemo@mba.ocn.ne.jp \
    --cc=drow@false.org \
    --cc=gdb@sourceware.org \
    /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