From: Eli Zaretskii <eliz@elta.co.il>
To: Roland McGrath <roland@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] add-symbol-file-from-memory command
Date: Mon, 02 Feb 2004 06:19:00 -0000 [thread overview]
Message-ID: <ullnmats0.fsf@elta.co.il> (raw)
In-Reply-To: <200402020338.i123cQks022042@magilla.sf.frob.com> (message from Roland McGrath on Sun, 1 Feb 2004 19:38:26 -0800)
> Date: Sun, 1 Feb 2004 19:38:26 -0800
> From: Roland McGrath <roland@redhat.com>
>
> This patch hasn't changed since the last time I posted it. But I'm hoping
> that it will be approved this time. This support (the underlying function,
> not the user command) is the last nontrivial piece required for backtraces
> from system calls to work right with vanilla Linux 2.6 kernels. The only
> objections previously were not apropos, and noone said anything about the
> content of the code itself. If there is valid cause not to put this in
> now, I hope I can see it stated clearly.
I have a couple of minor comments regarding the documentation and the
user interface:
> + c = add_cmd ("add-symbol-file-from-memory", class_files,
> + add_symbol_file_from_memory_command,
> + "Usage: add-symbol-file-from-memory ADDR\n\
> +Load the symbols out of memory from a dynamically loaded object file.\n\
> +ADDR is the starting address of the file's shared object file header.",
> + &cmdlist);
> +
There are two problems with this command definition:
. The first line of the doc string, up until the first \n, should
be a short description of the command, since that is what GDB
displays when several commands are listed (e.g., by `apropos' or
`help files' commands). [Yes, I know: `add-symbol-file' that is
already there has the same problem.]
. It is not entirely clear what could ADDR be. Is that a numerical
address, or something more flexible? The reason that this is
important is that the command's completion function should be set
according to the possible arguments it could accept; as written,
the command's completion will try to complete on symbol names,
which I'm not sure to be appropriate.
Also, if this code is approved, please add to the manual a
description of the new command.
TIA
P.S. This command is undocumented. Could someone of the symfile.c
maintainers please document it?
> c = add_cmd ("add-shared-symbol-files", class_files,
> add_shared_symbol_files_command,
> "Load the symbols from shared objects in the dynamic linker's link map.",
next prev parent reply other threads:[~2004-02-02 6:19 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-02 3:38 Roland McGrath
2004-02-02 4:06 ` Daniel Jacobowitz
2004-02-02 4:47 ` Roland McGrath
2004-02-02 15:02 ` Daniel Jacobowitz
2004-02-02 23:31 ` Roland McGrath
2004-02-02 23:34 ` Daniel Jacobowitz
2004-02-02 6:19 ` Eli Zaretskii [this message]
2004-02-02 7:35 ` Roland McGrath
2004-02-02 17:29 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2004-04-08 22:38 Roland McGrath
2004-04-15 18:11 ` Jim Blandy
2004-04-15 18:49 ` Andrew Cagney
2004-04-15 21:42 ` Roland McGrath
2004-04-08 20:47 Roland McGrath
2004-04-08 22:13 ` Jim Blandy
2004-04-08 22:28 ` Roland McGrath
2004-04-08 22:32 ` Daniel Jacobowitz
2004-04-08 22:35 ` Andrew Cagney
2004-04-08 22:42 ` Roland McGrath
2004-04-15 18:52 ` Andrew Cagney
2004-02-12 0:34 Roland McGrath
2004-02-13 15:54 ` Andrew Cagney
2004-02-13 19:13 ` Roland McGrath
2003-10-03 4:27 Roland McGrath
2003-10-03 21:41 ` Jim Blandy
2003-10-03 21:45 ` Daniel Jacobowitz
2003-10-03 22:08 ` Roland McGrath
2003-10-03 22:19 ` Elena Zannoni
2003-10-03 23:00 ` Roland McGrath
2003-10-04 12:57 ` Elena Zannoni
2003-10-04 20:14 ` Roland McGrath
2003-10-07 1:42 ` Andrew Cagney
2003-10-03 22:34 ` Andrew Cagney
2003-10-03 23:02 ` Roland McGrath
2003-10-04 14:39 ` Andrew Cagney
2003-10-06 15:30 ` Jim Blandy
2003-10-06 15:43 ` Daniel Jacobowitz
2003-10-06 19:57 ` Roland McGrath
2003-10-07 23:32 ` Michael Snyder
2003-05-20 7:01 Roland McGrath
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=ullnmats0.fsf@elta.co.il \
--to=eliz@elta.co.il \
--cc=gdb-patches@sources.redhat.com \
--cc=roland@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