Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Christian Eggers <ceggers@gmx.de>
Cc: gdb-patches@sourceware.org, Pedro Alves <palves@redhat.com>,
	Yao Qi <yao@codesourcery.com>
Subject: Re: [PATCH] Call remote_check_symbols() even if only symbol-file (not file) has been given
Date: Mon, 03 Feb 2014 02:19:00 -0000	[thread overview]
Message-ID: <20140203021856.GB4689@adacore.com> (raw)
In-Reply-To: <3438987.Z4RkDDzs8O@p2130>

Hello Christian,

On Sat, Feb 01, 2014 at 08:21:31AM +0100, Christian Eggers wrote:
> The Eclipse "C/C++ GDB Hardware Debugging" plugin runs only 
> the "symbol-file" command. In this case, remote_check_symbols()
> is not called and no qSymbol:: packet is sent to the gdbserver
> (OpenOCD in my case).
> 
> 2014-02-01  Christian Eggers  <ceggers@gmx.de>
> 
> 	* remote.c (remote_start_remote): Call remote_check_symbols() even if only symbol-file (not file) has been given.

With my Patch Champion hat...

The line above in the ChangeLog is too long and needs to be split at
around 70-80 characters.


> diff --git a/gdb/remote.c b/gdb/remote.c
> index 7297df0..40cc143 100644
> --- a/gdb/remote.c
> +++ b/gdb/remote.c
> @@ -3668,7 +3668,7 @@ remote_start_remote (int from_tty, struct target_ops *target, int extended_p)
>    /* If we connected to a live target, do some additional setup.  */
>    if (target_has_execution)
>      {
> -      if (exec_bfd) 	/* No use without an exec file.  */
> +      if (symfile_objfile) 	/* No use without an symbol-file.  */
>  	remote_check_symbols ();
>      }

"a symbol-file" (instead of "an")?

-- 
Joel


      reply	other threads:[~2014-02-03  2:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-01  7:21 Christian Eggers
2014-02-03  2:19 ` Joel Brobecker [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=20140203021856.GB4689@adacore.com \
    --to=brobecker@adacore.com \
    --cc=ceggers@gmx.de \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.com \
    --cc=yao@codesourcery.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