This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: [RFA] Locate sparc64 arguments correctly
- From: Kevin Buettner <kevinb at redhat dot com>
- To: "David S. Miller" <davem at redhat dot com>, gdb-patches at sources dot redhat dot com
- Date: Tue, 23 Apr 2002 16:09:40 -0700
- Subject: Re: [RFA] Locate sparc64 arguments correctly
- References: <20020420.020906.44150275.davem@redhat.com>
On Apr 20, 2:09am, David S. Miller wrote:
> 1) Debugging information encodes LOC_ARG/LOC_REF_ARG offsets
> with the Sparc64 stack bias included, we keep track of the
> frame pointer with the stack bias removed on sparc64.
>
> sparc64_frame_args_address takes care of that.
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?