From: Eric Christopher <echristo@apple.com>
To: Thiemo Seufer <ths@networkno.de>
Cc: binutils@sourceware.org
Subject: Re: [PATCH] Force mips16 disassembled addresses to odd values
Date: Fri, 28 Apr 2006 20:36:00 -0000 [thread overview]
Message-ID: <E5F4E6E9-9E75-4822-B6FA-A02362CA9339@apple.com> (raw)
In-Reply-To: <20060428181432.GK4579@networkno.de>
On Apr 28, 2006, at 11:14 AM, Thiemo Seufer wrote:
> Eric Christopher wrote:
>>
>> On Apr 28, 2006, at 5:33 AM, Thiemo Seufer wrote:
>>
>>> Hello All,
>>>
>>> this patch forces some disassembled mips16 addresses to odd values,
>>> this helps gdb to handle mips16 code better.
>>
>> Uh. What on earth? Could you explain this one? :)
>
> Gdb has to find out what part is MIPS16 in mixed MIPS32/MIPS16 code
> binaries. The code is used in MIPS' SDE6 toolchain, I don't know if
> there are better ways like relying on DWARF info (in a detached file
> for raw binaries?).
Good question. What's done for arm/thumb?
-eric
next prev parent reply other threads:[~2006-04-28 18:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-28 16:37 Thiemo Seufer
2006-04-28 19:29 ` Eric Christopher
2006-04-28 19:39 ` Thiemo Seufer
2006-04-28 20:36 ` Eric Christopher [this message]
2006-04-29 3:12 ` Daniel Jacobowitz
2006-04-29 6:14 ` Eric Christopher
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=E5F4E6E9-9E75-4822-B6FA-A02362CA9339@apple.com \
--to=echristo@apple.com \
--cc=binutils@sourceware.org \
--cc=ths@networkno.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).