Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: "Maciej W. Rozycki" <macro@mips.com>
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 17:50:00 -0000	[thread overview]
Message-ID: <20071217174645.GA6476@caradoc.them.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0712171734350.31562@perivale.mips.com>

On Mon, Dec 17, 2007 at 05:37:44PM +0000, Maciej W. Rozycki wrote:
> On Sun, 16 Dec 2007, Daniel Jacobowitz wrote:
> 
> > OK.  This routine is used by MI, but should not be - a long term TODO
> > item is to change the way we present frame IDs to MI frontends to not
> > be based on the stack pointer, and then its use will go away.  But
> > that's not going to happen too soon.
> 
>  What about Insight?  Not that I would die for it, but the function is 
> called from a few places in gdbtk/generic/gdbtk-{cmds,stack,varobj}.c and 
> given the amount of development done on Insight these days I would imagine 
> these uses are not going to go away anytime soon.

Right.  I'm not going to touch it; I don't know what Insight uses it
for, or whether it should.  But it's probably using it for the same
reason MI is, since Insight predates varobjs.

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.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2007-12-17 17:47 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 [this message]
2007-12-17 18:35       ` Maciej W. Rozycki

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=20071217174645.GA6476@caradoc.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=macro@linux-mips.org \
    --cc=macro@mips.com \
    --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