From: "Maciej W. Rozycki" <macro@mips.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sourceware.org, Nigel Stephens <nigel@mips.com>,
"Maciej W. Rozycki" <macro@linux-mips.org>
Subject: Re: utils.c: Sign-extend addresses if required by the target
Date: Mon, 17 Dec 2007 18:35:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.61.0712171749250.31562@perivale.mips.com> (raw)
In-Reply-To: <20071217174645.GA6476@caradoc.them.org>
On Mon, 17 Dec 2007, Daniel Jacobowitz wrote:
> I try not to break Insight knowingly, but if we go to clean up MI
> frame identification and that breaks Insight, I'll leave it to the
> Insight developers to clean up. That's the downside of being so
> tightly tied into GDB.
OK, thanks for this clarification. I have applied this change thus.
Maciej
prev parent reply other threads:[~2007-12-17 17:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-22 16:25 Maciej W. Rozycki
2007-12-16 21:43 ` Daniel Jacobowitz
2007-12-17 17:47 ` Maciej W. Rozycki
2007-12-17 17:50 ` Daniel Jacobowitz
2007-12-17 18:35 ` Maciej W. Rozycki [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=Pine.LNX.4.61.0712171749250.31562@perivale.mips.com \
--to=macro@mips.com \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=macro@linux-mips.org \
--cc=nigel@mips.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