Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Claudia Salzberg <salzberg@us.ibm.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: Daniel THOMPSON <daniel.thompson@st.com>, gdb@sources.redhat.com
Subject: Re: unable to debug remotely with threads on ppc target with gdb6.1/6.3
Date: Tue, 12 Apr 2005 16:35:00 -0000	[thread overview]
Message-ID: <OF082AA560.29535A7A-ON87256FE1.005812D8-86256FE1.005B279A@us.ibm.com> (raw)
In-Reply-To: <20050412120620.GA6951@nevyn.them.org>

>That's not Claudia's problem; the above only applies to NPTL, and she
>appears to be using LinuxThreads from the error logs.

Indeed I was misusing the commands to specify files.  The command 'file' 
cannot be used after connecting from gdb to a remoter gdbserver since the 
program is considered at that point to be running.  Because of this I used 
'add-symbol-file' which purportedly (or so I thought) allowed me to add a 
symbol file to an already running process.  However, this command should 
be used when the file specified has already been dynamically loaded 
(perhaps when a stripped executable is being run?).  Not sure how it works 
internally yet but the point is the 'file' command should be used to read 
symbols.  When using gdbserver, this command should be used prior to 
connecting remotely to the server to avoid the 'program already running' 
complaint.

Thanks for your help!  (now I'm tempted to try using NPTL ;) )

Claudia A. Salzberg
Linux Technology Center
salzberg@us.ibm.com



      reply	other threads:[~2005-04-12 16:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-11 16:29 Claudia Salzberg
2005-04-11 16:37 ` Daniel Jacobowitz
2005-04-12  7:52 ` Daniel THOMPSON
2005-04-12 12:06   ` Daniel Jacobowitz
2005-04-12 16:35     ` Claudia Salzberg [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=OF082AA560.29535A7A-ON87256FE1.005812D8-86256FE1.005B279A@us.ibm.com \
    --to=salzberg@us.ibm.com \
    --cc=daniel.thompson@st.com \
    --cc=drow@false.org \
    --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