Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: Tom Tromey <tromey@redhat.com>
Subject: Re: RFA: fix PR mi/8138
Date: Tue, 11 Jan 2011 00:07:00 -0000	[thread overview]
Message-ID: <201101110007.33006.pedro@codesourcery.com> (raw)
In-Reply-To: <m3k4icldkz.fsf@fleche.redhat.com>

On Monday 10 January 2011 20:15:56, Tom Tromey wrote:
> +@table @samp
> +@item from
> +@itemx to
> +These items, if provided, are a range of addresses belonging to this
> +shared library.

> +^done,sharedlibs=[lib=[from="0x00111360",to="0x00111498",syms-read="2",name="/lib/libexample.so"]]

The =library-loaded event was added with the "from" and "to"
fields left out on purpose.  I think that this command should
be consistent with the event.  The event outputs both target and
host paths to the shared library, this prints only a single "name".

I'm not objecting, but I'm almost certain that I remember
someone bringing up that this MI command was missing, but
it was then mentioned that there's no real need for it
since the frontend should be getting everything it needs
from the =library-loaded / =library-unloaded events.
(This PR predates these events by a few years).

> +void
> +mi_cmd_file_list_shared_libraries (char *command, char **argv, int argc)
> +{
> +  if (!mi_valid_noargs ("mi_cmd_file_list_shared_libraries", argc, argv))
> +    error (_("mi_cmd_file_list_shared_libraries: Usage: No args"));

These errors should not show GDB's function name, but instead the MI command
name.  We have many instances of this issue, but we have been fasing them
out, and avoiding introducing new ones.

-- 
Pedro Alves


  reply	other threads:[~2011-01-11  0:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-10 20:16 Tom Tromey
2011-01-11  0:07 ` Pedro Alves [this message]
2011-01-12 20:57   ` Tom Tromey
2011-01-12 21:23     ` Pedro Alves
2011-02-04 16:18   ` Tom Tromey
2011-02-04 16:35     ` Daniel Jacobowitz
2011-01-11  4:01 ` Eli Zaretskii

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=201101110007.33006.pedro@codesourcery.com \
    --to=pedro@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tromey@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