Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Albert Ho <alberth@intellambda.com>
Cc: gdb@sources.redhat.com
Subject: Re: gdb-6.0/gdb/gdbserver/target.c::set_desired_inferior()
Date: Fri, 27 Feb 2004 20:15:00 -0000	[thread overview]
Message-ID: <20040227201519.GA12740@nevyn.them.org> (raw)
In-Reply-To: <403FA498.3020907@intellambda.com>

On Fri, Feb 27, 2004 at 12:12:08PM -0800, Albert Ho wrote:
> I am trying to decide whether the problem is in the thread library or gdb.
> 4 facts:
> 1) The program runs fine on its own.
> 2) gdbserver can debug the program if let the process starts first 
> (hence loading all the library), then use --attach.
> 3) Run gdb gdbserver, then start the program in gdbserver also works.
> 4) Run gdbserver alone with the program cause the program's new thread 
> died, I suspect it affects gdbserver to segfault too.
> 
> I'll get the pthread symbol to look further.
> 
> One last question. Does the host suppose to load exactly the same 
> library as the target? I see the host loads libthread.so.1, but the 
> target's core has libthread_db.so.1.

The host should load a copy of libpthread.so.1 which matches the copy
loaded by the target application (NOT gdbserver, gdbserver will load
libthread_db.so.1).

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


      reply	other threads:[~2004-02-27 20:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-27  3:22 gdb-6.0/gdb/gdbserver/target.c::set_desired_inferior() Albert Ho
2004-02-27  3:24 ` gdb-6.0/gdb/gdbserver/target.c::set_desired_inferior() Daniel Jacobowitz
2004-02-27 20:02   ` gdb-6.0/gdb/gdbserver/target.c::set_desired_inferior() Albert Ho
2004-02-27 20:04     ` gdb-6.0/gdb/gdbserver/target.c::set_desired_inferior() Daniel Jacobowitz
2004-02-27 20:11       ` gdb-6.0/gdb/gdbserver/target.c::set_desired_inferior() Albert Ho
2004-02-27 20:15         ` 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=20040227201519.GA12740@nevyn.them.org \
    --to=drow@false.org \
    --cc=alberth@intellambda.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