public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] disassembler ?
Date: Thu, 16 May 2013 19:18:45 +0200	[thread overview]
Message-ID: <20130516191845.385b1df0@lilith> (raw)
In-Reply-To: <CAPKZHbVOpoLNHAsjfwyEi9783zgYbfNuf9_GZ=AVuXTmEwSy_g@mail.gmail.com>

Hi Brad,

On Thu, 16 May 2013 10:45:47 -0600, Brad Walker <bwalker@musings.com>
wrote:

> I noticed there is no support for a disassembler except for BedBug.
>
> I am working on a new processor and board for that processor. I'm in need
> of a disassembler for this work.
> 
> I was thinking about adding a cmd_dis.c file as a stub and make the
> implementation exist in board/..
> 
> Is this the right way to go as we are willing to release our code back to
> the community once it is completed. Ideas/comments about this are
> appreciated.

There is little too no point in having a disassembler command in U-Boot,
when one can usually talk to the target with a debugging probe that
will work with gdb, and thus allow using gdd's own disassembler.

(also, out of the target, objdump can disassemble an ELF binary)

The best location IMO for putting the disassembler is by adding support
for your new processor to gcc/gdb/objdump so that you have it not only
for U-Boot but for any other code you care to build for this processor.

> -brad w.

Amicalement,
-- 
Albert.

  reply	other threads:[~2013-05-16 17:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-16 16:45 [U-Boot] disassembler ? Brad Walker
2013-05-16 17:18 ` Albert ARIBAUD [this message]
2013-05-16 22:15 ` Wolfgang Denk
2013-05-23 17:13   ` Brad Walker
2013-05-23 18:53     ` Albert ARIBAUD
2013-05-23 19:08       ` Peter Barada
2013-05-23 19:49         ` Albert ARIBAUD
2013-05-23 20:56           ` Peter Barada
2013-05-23 21:09     ` Wolfgang Denk

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=20130516191845.385b1df0@lilith \
    --to=albert.u.boot@aribaud.net \
    --cc=u-boot@lists.denx.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