From: Michael Snyder <msnyder@specifix.com>
To: Vinicius Nunes Pinto <vinicius.pinto@eldorado.org.br>
Cc: gdb@sourceware.org
Subject: Re: Debug Symbols from GDB Server
Date: Wed, 07 May 2008 19:49:00 -0000 [thread overview]
Message-ID: <1210189755.4615.471.camel@localhost.localdomain> (raw)
In-Reply-To: <AC2729D6E3A3314A922E4E0FBE513F65016E0A79@MAIL.eldorado.org.br>
On Wed, 2008-05-07 at 16:08 -0300, Vinicius Nunes Pinto wrote:
> I want to debug an application that is running remotely. My problem is
> that I don't have a copy of the symbol's file at the client, just on the
> host. I am also not able to use the command "remote get targetfile
> hostfile".
>
> Does anyone know how to retrieve the debug symbols (and load the
> symbols' tables) from the target by GDB server?
Can't be done. You need to somehow get a copy of the
remote symbol file onto the host where you run gdb.
That's just how it's done. ;-/
prev parent reply other threads:[~2008-05-07 19:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-07 19:08 Vinicius Nunes Pinto
2008-05-07 19:11 ` Daniel Jacobowitz
2008-05-07 19:49 ` Michael Snyder [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=1210189755.4615.471.camel@localhost.localdomain \
--to=msnyder@specifix.com \
--cc=gdb@sourceware.org \
--cc=vinicius.pinto@eldorado.org.br \
/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