Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <dmj+@andrew.cmu.edu>
To: Andrew Cagney <ac131313@cygnus.com>, gdb-patches@sources.redhat.com
Subject: Re: [rfa] mips heuristic_proc_start fix
Date: Fri, 06 Jul 2001 11:40:00 -0000	[thread overview]
Message-ID: <20010706114028.A6366@nevyn.them.org> (raw)
In-Reply-To: <20010706113232.A6209@nevyn.them.org>

On Fri, Jul 06, 2001 at 11:32:32AM -0700, Daniel Jacobowitz wrote:
> On Fri, Jul 06, 2001 at 02:27:23PM -0400, Andrew Cagney wrote:
> > > This one was fun to track down... I've been getting corrupt PC values off
> > > the stack in backtraces, something which needs to be fixed elsewhere.  The
> > > interesting thing is that the PC I was reading was 0x2.  Remember that
> > > CORE_ADDR on MIPS is an unsigned 64-bit quantity.
> > 
> > 
> > You mean ***SIGNED** right?
> 
> Glarg.  Yes, it's signed, of course!  Let me peer at this for a moment
> and see why the math was coming out wrong; the patch is correct, but
> now it's not quite as obvious to me why :)

No, I stand uncorrected:

(gdb) ptype CORE_ADDR
type = long long unsigned int

It's sign extended as if it were signed, but the type itself is not!


typedef BFD_HOST_U_64_BIT bfd_vma;
typedef BFD_HOST_64_BIT bfd_signed_vma;

and

typedef bfd_vma CORE_ADDR;

-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2001-07-06 11:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-06 11:20 Daniel Jacobowitz
2001-07-06 11:27 ` Andrew Cagney
2001-07-06 11:32   ` Daniel Jacobowitz
2001-07-06 11:40     ` Daniel Jacobowitz [this message]
2001-07-12  0:47       ` Andrew Cagney
2001-07-12 12:14         ` Daniel Jacobowitz
2001-07-12 14:11           ` Andrew Cagney
2001-07-12 14:19             ` Daniel Jacobowitz
2001-07-12 14:35               ` Andrew Cagney

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=20010706114028.A6366@nevyn.them.org \
    --to=dmj+@andrew.cmu.edu \
    --cc=ac131313@cygnus.com \
    --cc=gdb-patches@sources.redhat.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