Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Andrew Burgess <andrew.burgess@embecosm.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb: Add support for dumping to verilog hex format.
Date: Wed, 22 Apr 2015 22:33:00 -0000	[thread overview]
Message-ID: <553821B2.1080704@redhat.com> (raw)
In-Reply-To: <ac8db75957e27b34d78e2f0b692b5072a9809a37.1429740646.git.andrew.burgess@embecosm.com>

Hi Andrew,

On 04/22/2015 11:24 PM, Andrew Burgess wrote:
> This patch extends the 'dump' command to generate output in the
> verilog hex format supported by bfd.
> 
> OK to apply?

Sounds like gdb.base/dump.exp should be extended to cover this?

Thanks,
Pedro Alves


  reply	other threads:[~2015-04-22 22:33 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 [this message]
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

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=553821B2.1080704@redhat.com \
    --to=palves@redhat.com \
    --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