From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sources.redhat.com
Subject: Re: [rfa/remote] Reread symbols on 'target remote'
Date: Tue, 23 Mar 2004 16:47:00 -0000 [thread overview]
Message-ID: <20040323164753.GB21830@nevyn.them.org> (raw)
In-Reply-To: <406068DB.30007@gnu.org>
On Tue, Mar 23, 2004 at 11:42:03AM -0500, Andrew Cagney wrote:
> I was thinking of something more agressive:
>
> if target (via /proc) can identify exec file
> switch to target's exec file, load
> else if exec file known
> load
> else
> hope the user knows what they are doing
> fi
I don't think that's a good idea. For example, recently, I was running
/usr/bin/gdb. It got stuck in a loop. I attached, but could not get a
backtrace - it was stripped - so I detached, loaded
/nevyn/local/gdb/gdb-6.0/objdir/gdb/gdb, and attached. Then I had my
backtrace. Your proposed change above would have made GDB switch back
to the stripped version.
Sure, separate debug info is a nice solution to this - if you've
prepared it in advance.
> however yes, at least (per your patch) always loading the symbols is a
> good first step.
OK, I'm checking it in for HEAD.
> (this goes back to earlier posts where we need to overaul the target
> stack so that multiple instances are available)
Absolutely agreed.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2004-03-23 16:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-28 17:39 Daniel Jacobowitz
2004-03-05 5:31 ` Andrew Cagney
2004-03-06 23:54 ` Daniel Jacobowitz
2004-03-17 15:16 ` Andrew Cagney
2004-03-19 0:09 ` Andrew Cagney
2004-03-19 0:09 ` Daniel Jacobowitz
2004-03-17 16:51 ` Daniel Jacobowitz
2004-03-22 22:28 ` Andrew Cagney
2004-03-23 15:50 ` Daniel Jacobowitz
2004-03-23 16:42 ` Andrew Cagney
2004-03-23 16:47 ` Daniel Jacobowitz [this message]
2004-03-19 0:09 ` Daniel Jacobowitz
2004-03-19 0:09 ` Andrew Cagney
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=20040323164753.GB21830@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@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