Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: kevinb@redhat.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Locate sparc64 arguments correctly
Date: Wed, 24 Apr 2002 08:33:00 -0000	[thread overview]
Message-ID: <20020424.082353.15613374.davem@redhat.com> (raw)
In-Reply-To: <1020423230940.ZM10851@localhost.localdomain>

   From: Kevin Buettner <kevinb@redhat.com>
   Date: Tue, 23 Apr 2002 16:09:40 -0700

   I agree that this is the problem, but, when you do this...
   
   > +/* Debugging information stores LOC_ARG/LOC_REF_ARG offsets with the
   > +   sparc64 stack bias present, this undoes that so that users of
   > +   FRAME_ARGS_ADDRESS use the right location.  */
   > +
   > +static CORE_ADDR
   > +sparc64_frame_args_address (struct frame_info *fi)
   > +{
   > +  return fi->frame - 2047;
   > +}
   
   ...does the output from ``info frame'' still look reasonable?
   
You're right, it does the wrong thing for info frame.

This indicates that FRAME_ARGS_ADDRESS is being used for two entirely
different purposes.  One is to interpret debugging information, the
other is to print arguments on the stack via info frame.

This particular case would be cured by adjusting what we use for
FRAME_ARGS_SKIP on a 64-bit sparc target such that the STACK bias is
calcelled back out.  I will make that modification to my patch and
resubmit.

Thanks for pointing this out.


  reply	other threads:[~2002-04-24 15:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-20  2:17 David S. Miller
2002-04-23 12:53 ` Michael Snyder
2002-04-23 21:57   ` David S. Miller
2002-04-23 16:09 ` Kevin Buettner
2002-04-24  8:33   ` David S. Miller [this message]
2002-04-24  9:42     ` Kevin Buettner
2002-04-24  9:53       ` David S. Miller

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=20020424.082353.15613374.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=kevinb@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