From: Mike Frysinger <vapier@gentoo.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: toolchain-devel@blackfin.uclinux.org, gdb-patches@sourceware.org
Subject: Re: [toolchain-devel] [PATCH v2] sim: add --map-info option
Date: Wed, 15 Dec 2010 12:02:00 -0000 [thread overview]
Message-ID: <AANLkTimh=VqZGVYve+Mv2fKnuE8WN3JSd78pOdA5uXwy@mail.gmail.com> (raw)
In-Reply-To: <20101215114747.GB2596@adacore.com>
On Wed, Dec 15, 2010 at 06:47, Joel Brobecker wrote:
>> > One last request: Can you send a patch adding a note in the gdb/NEWS file?
>>
>> to mention the new sim option --map-info ? i didnt think new sim
>> options were announced in the gdb/NEWS file as i didnt see any
>> examples of this ...
>
> Yes. I think it's NEWS-worthy, regardless of what we have (or not)
> been doing in the past.
>
> Also, since there does not seem to be any sim documentation in the GDB
> Manual, the only way I could think of to give this new option a tiny bit
> of exposure is the NEWS file.
hows this ?
--- NEWS 10 Dec 2010 20:33:44 -0000 1.414
+++ NEWS 15 Dec 2010 12:01:10 -0000
@@ -115,6 +115,10 @@
* Guile support was removed.
+* New features in the GNU simulator
+
+ ** The --map-info flag lists all known core mappings.
+
*** Changes in GDB 7.2
* Shared library support for remote targets by default
-mike
next prev parent reply other threads:[~2010-12-15 12:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-01 16:15 [PATCH] " Mike Frysinger
2010-12-14 7:36 ` Joel Brobecker
2010-12-14 15:17 ` Mike Frysinger
2010-12-14 18:34 ` Mike Frysinger
2010-12-14 18:50 ` Pedro Alves
2010-12-14 19:03 ` Mike Frysinger
2010-12-14 19:12 ` Pedro Alves
2010-12-14 19:30 ` Mike Frysinger
2010-12-15 4:54 ` Joel Brobecker
2010-12-15 11:50 ` Mike Frysinger
2010-12-14 18:37 ` [PATCH v2] " Mike Frysinger
2010-12-15 5:02 ` Joel Brobecker
2010-12-15 11:21 ` Mike Frysinger
2010-12-15 11:48 ` Joel Brobecker
2010-12-15 12:02 ` Mike Frysinger [this message]
2010-12-15 13:16 ` [toolchain-devel] " 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='AANLkTimh=VqZGVYve+Mv2fKnuE8WN3JSd78pOdA5uXwy@mail.gmail.com' \
--to=vapier@gentoo.org \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=toolchain-devel@blackfin.uclinux.org \
/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