From: Eli Zaretskii <eliz@gnu.org>
To: Andrew Burgess <andrew.burgess@embecosm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb: Add support for dumping to verilog hex format.
Date: Thu, 23 Apr 2015 06:18:00 -0000 [thread overview]
Message-ID: <838udj2wru.fsf@gnu.org> (raw)
In-Reply-To: <ac8db75957e27b34d78e2f0b692b5072a9809a37.1429740646.git.andrew.burgess@embecosm.com>
> From: Andrew Burgess <andrew.burgess@embecosm.com>
> Cc: Andrew Burgess <andrew.burgess@embecosm.com>
> Date: Wed, 22 Apr 2015 23:24:59 +0100
>
> diff --git a/gdb/NEWS b/gdb/NEWS
> index 62cbdcb..6ad68ac 100644
> --- a/gdb/NEWS
> +++ b/gdb/NEWS
> @@ -42,6 +42,8 @@
> (no "set sysroot" or "file" commands are required). See "New remote
> packets" below.
>
> +* The "dump" command now supports verilog hex format.
This part is OK.
> static void
> +verilog_dump_command (char *cmd, int from_tty)
> +{
> + printf_unfiltered ("\"dump verilog\" must be followed by a subcommand.\n");
Shouldn't this message be in _()?
> diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
> index 0410702..4b78fb4 100644
> --- a/gdb/doc/gdb.texinfo
> +++ b/gdb/doc/gdb.texinfo
> @@ -10890,6 +10890,8 @@ Intel hex format.
> Motorola S-record format.
> @item tekhex
> Tektronix Hex format.
> +@item verilog
> +Verilog Hex format.
> @end table
>
> @value{GDBN} uses the same definitions of these formats as the
OK for this part.
Thanks.
prev parent reply other threads:[~2015-04-23 6:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-22 22:25 Andrew Burgess
2015-04-22 22:33 ` Pedro Alves
2015-04-22 23:04 ` Andrew Burgess
2015-04-23 10:41 ` Pedro Alves
2015-04-23 21:31 ` Andrew Burgess
2015-04-24 6:17 ` Eli Zaretskii
2015-04-24 13:50 ` Pedro Alves
2015-04-23 21:34 ` Andrew Burgess
2015-04-24 13:51 ` Pedro Alves
2015-04-23 6:18 ` Eli Zaretskii [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=838udj2wru.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=andrew.burgess@embecosm.com \
--cc=gdb-patches@sourceware.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