From: "Frank Ch. Eigler" <fche@redhat.com>
To: Stephen Done <stephen.done@cw.com>
Cc: cgen@sources.redhat.com
Subject: Re: Using CGEN Disassembler
Date: Wed, 21 Nov 2001 07:46:00 -0000 [thread overview]
Message-ID: <20011121104612.A30770@redhat.com> (raw)
Message-ID: <20011121074600.Y6u4ibIcQFsvsSAJ71apOIEj8VaJMF53-QsznDRG_kU@z> (raw)
In-Reply-To: <ICEBKEBHKLMIFEDLONLMCEJNCCAA.stephen.done@cw.com>
Hi -
On Wed, Nov 21, 2001 at 02:45:27PM -0000, Stephen Done wrote:
: I would like to use CGEN to disassemble some code for the Mitsubishi M32R
: processor.
: [...]
: All I need is the command to take a binary file and convert it to assembler.
: I've done as much RTFM'ing as I can, and I'm not getting anywhere.
Thanks for looking into it before asking the question!
Why do you think you need to deal with cgen directly for this task?
Are you aware that if you compile a m32r cross toolchain (or at least
binutils), you get an objdump program that can disassemble stuff for you?
cvs [...] co binutils
/[src]/configure --target=m32r-elf --prefix=[installtree]
make all install
[installtree]/bin/m32r-elf-objdump -d program.elf
- FChE
--
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE7+8xDVZbdDOm/ZT0RAhu4AJ9rQ4NlAmSMNvZ5ihu7+gLDGVNqawCfYCpg
6n+Ym8ZMhPBBGf6DdxwK+KA=
=Y4Xv
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2001-11-21 7:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-25 12:26 Stephen Done
2001-10-29 10:37 ` Greg McGary
2001-11-04 19:57 ` Stephen Done
2001-11-06 8:48 ` Greg McGary
2001-11-21 8:07 ` Greg McGary
2001-11-21 7:24 ` Stephen Done
2001-11-21 6:57 ` Greg McGary
2001-11-05 4:10 ` Frank Ch. Eigler [this message]
2001-11-05 17:03 ` Stephen Done
2001-11-21 7:54 ` Stephen Done
2001-11-21 7:46 ` Frank Ch. Eigler
2001-11-06 11:07 ` Alan Lehotsky
2001-11-06 10:48 ` Stephen Done at home
2001-11-21 17:39 ` Stephen Done@home
2001-11-23 6:35 ` Alan Lehotsky
2001-11-21 6:45 ` Stephen Done
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=20011121104612.A30770@redhat.com \
--to=fche@redhat.com \
--cc=cgen@sources.redhat.com \
--cc=stephen.done@cw.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).