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

> 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).

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)?

Andrew



WARNING: multiple messages have this Message-ID
From: Andrew Cagney <cagney@gnu.org>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa/remote] Reread symbols on 'target remote'
Date: Fri, 19 Mar 2004 00:09:00 -0000	[thread overview]
Message-ID: <40586BC3.1080706@gnu.org> (raw)
Message-ID: <20040319000900.tedfmnNc_NK0cVHYRI9S3fdPHE1rm5FYqTkGClvneXQ@z> (raw)
In-Reply-To: <20040306235436.GA10071@nevyn.them.org>

> 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).

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)?

Andrew



  reply	other threads:[~2004-03-17 15:16 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 [this message]
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
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=40586BC3.1080706@gnu.org \
    --to=cagney@gnu.org \
    --cc=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