Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Andrew Cagney <cagney@gnu.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa/remote] Reread symbols on 'target remote'
Date: Wed, 17 Mar 2004 16:51:00 -0000	[thread overview]
Message-ID: <20040317165115.GA8390@nevyn.them.org> (raw)
Message-ID: <20040317165100.mYS3swX6DEpEW7rRc0Sc0EoagYBoKf-MZstw8xR_MoY@z> (raw)
In-Reply-To: <40586BC3.1080706@gnu.org>

On Wed, Mar 17, 2004 at 10:16:19AM -0500, Andrew Cagney wrote:
> >On Fri, Mar 05, 2004 at 12:31:46AM -0500, Andrew Cagney wrote:
> >
> >>>>>2004-02-28  Daniel Jacobowitz  <drow@mvista.com>
> >>>>>
> >>>>>	* remote.c (remote_open_1): Reopen the exec file and reread symbols
> >>>>>	if necessary.
> >>
> >>>
> >>>What happens if the target is "extended-remote"?
> >
> >
> >Works fine.  remote_open_1 is only called when we create the initial
> >connection and handles any rereading at that time; run_command in
> >infcmd.c will handle if the "run" command is issued over an existing
> >extended-remote connection.
> 
> Sorry, I ment without the patch (but I think you've answered that anyway).

Yeah - with extended-remote we don't reload on target extended-remote
but do reload on run.

> While "run" and "load" are fairly obvious sync points for GDB and its 
> executable I'm not sure that "target remote" is - it's behavior is kind 
> of sort of a screwed up version of attach.
> 
> What does that do (as far as I can tell it doesn't re-read symbols)?

I think you're right - attach won't reread symbols either.  I believe
run is the only current sync point.  My instinct is that target remote
and attach both ought to be - I know that if I'm debugging something
that needs to be started in a separate environment and attached to, and
I detach, rebuilt, re-attach, I'd be confused if GDB didn't
auto-reload.  I know I've tried to do the same thing for target remote,
and expected GDB to reload - it didn't, and it took me a while to work
out what the problem was.

We should probably be consistent.  Want me to get attach too?

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2004-03-17 16:51 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       ` Daniel Jacobowitz [this message]
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
2004-03-19  0:09       ` Andrew Cagney
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=20040317165115.GA8390@nevyn.them.org \
    --to=drow@false.org \
    --cc=cagney@gnu.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