From: Andrew Cagney <cagney@gnu.org>
To: Stefan Weyergraf <stefan@weyergraf.de>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] implements MI "-file-list-exec-sections" (updated)
Date: Fri, 07 May 2004 01:20:00 -0000 [thread overview]
Message-ID: <409AA124.6050601@gnu.org> (raw)
In-Reply-To: <200404222356.57808.stefan@weyergraf.de>
Lets separate out a few simpler parts:
----
Index: doc/gdb.texinfo
> ===================================================================
> RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
> retrieving revision 1.202
> diff -u -3 -p -r1.202 gdb.texinfo
> --- doc/gdb.texinfo 28 Mar 2004 12:22:55 -0000 1.202
> +++ doc/gdb.texinfo 22 Apr 2004 21:44:09 -0000
> @@ -14574,7 +14574,7 @@ Elena Zannoni.
>
> @item @var{mi-command} @expansion{}
> @code{[ @var{token} ] "-" @var{operation} ( " " @var{option} )*
> -@code{[} " --" @code{]} ( " " @var{parameter} )* @var{nl}}
> +[ " --" ] ( " " @var{parameter} )* @var{nl}}
>
> @item @var{token} @expansion{}
> "any sequence of digits"
> @@ -14698,13 +14698,13 @@ depending on the needs---this is still i
> @code{@var{console-stream-output} | @var{target-stream-output} | @var{log-stream-output}}
>
> @item @var{console-stream-output} @expansion{}
> -@code{"~" @var{c-string}}
> +@code{"~" @var{c-string} @var{nl}}
>
> @item @var{target-stream-output} @expansion{}
> -@code{"@@" @var{c-string}}
> +@code{"@@" @var{c-string} @var{nl}}
>
> @item @var{log-stream-output} @expansion{}
> -@code{"&" @var{c-string}}
> +@code{"&" @var{c-string} @var{nl}}
>
> @item @var{nl} @expansion{}
> @code{CR | CR-LF}
This part all looks correct, can you just post it separatly with a
ChangeLog.
----
> -static void core_files_info (struct target_ops *);
> +static void core_files_info (struct target_ops *, struct ui_out *);
Again, just this part (through out) is all ok, can you please post it.
----
Now the fun bit ...
You'll have noticed I sent out an e-mail asking about ``inferior vs
target'', lets ignore that question for this output...
> +@smallexample
> +(@value{GDBP})
> +123-file-list-exec-sections
> +~"Symbols from \"/var/home/ouk/projects/ht20/testproject/test-g\".\n"
> +123^done,targets=[
List of targets reflecting the target stack, nice.
{target-type-long="Local exec file",target-type-short="exec",
here ``target-'' is implied, so would just:
short-name=
long-name=
entry-point=
be better?
> +filename="/var/home/ouk/projects/ht20/testproject/test-g",file-type="elf32-i386",
> +target-entrypoint="0x08048380",sections=[
List of sections, again nice.
> +{start-address="0x08048134",end-address="0x08048147",section-name=".interp"},
> +{start-address="0x08048148",end-address="0x08048168",section-name=".note.ABI-tag"},
> +{start-address="0x08048168",end-address="0x08048198",section-name=".hash"},
> +{start-address="0x08048198",end-address="0x08048208",section-name=".dynsym"},
> +{start-address="0x08048208",end-address="0x080482af",section-name=".dynstr"},
> +{start-address="0x080482b0",end-address="0x080482be",section-name=".gnu.version"},
> +{start-address="0x080482c0",end-address="0x08048300",section-name=".gnu.version_r"},
> +{start-address="0x08048300",end-address="0x08048308",section-name=".rel.dyn"},
> +{start-address="0x08048308",end-address="0x08048320",section-name=".rel.plt"},
> +{start-address="0x08048320",end-address="0x08048337",section-name=".init"},
> +{start-address="0x08048338",end-address="0x08048378",section-name=".plt"},
> +{start-address="0x08048380",end-address="0x08048570",section-name=".text"},
> +{start-address="0x08048570",end-address="0x0804858b",section-name=".fini"},
> +{start-address="0x0804858c",end-address="0x080485a0",section-name=".rodata"},
> +{start-address="0x080485a0",end-address="0x080485b4",section-name=".eh_frame_hdr"},
> +{start-address="0x080485b4",end-address="0x080485f0",section-name=".eh_frame"},
> +{start-address="0x080495f0",end-address="0x080495fc",section-name=".data"},
> +{start-address="0x080495fc",end-address="0x080496dc",section-name=".dynamic"},
> +{start-address="0x080496dc",end-address="0x080496e4",section-name=".ctors"},
> +{start-address="0x080496e4",end-address="0x080496ec",section-name=".dtors"},
> +{start-address="0x080496ec",end-address="0x080496f0",section-name=".jcr"},
> +{start-address="0x080496f0",end-address="0x0804970c",section-name=".got"},
> +{start-address="0x0804970c",end-address="0x08049710",section-name=".bss"}]}]
> +(@value{GDBP})
> +@end smallexample
I like it. But lets get the other changes in first.
Sorry for the delay.
Andrew
next prev parent reply other threads:[~2004-05-07 1:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-22 21:56 Stefan Weyergraf
2004-04-22 22:22 ` Bob Rossi
2004-04-22 23:31 ` Stefan Weyergraf
2004-04-28 21:51 ` Andrew Cagney
2004-05-07 1:20 ` Andrew Cagney [this message]
2004-05-06 22:07 ` Stefan Weyergraf
2004-05-12 20:14 ` Andrew Cagney
2004-04-30 21:54 Nick Roberts
2004-05-01 4:09 ` Bob Rossi
2004-05-01 12:08 ` Nick Roberts
2004-05-02 13:25 ` Bob Rossi
2004-05-07 1:19 ` 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=409AA124.6050601@gnu.org \
--to=cagney@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=stefan@weyergraf.de \
/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