Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Mueller <m.mueller99@kay-mueller.de>
To: Mark Kettenis <kettenis@chello.nl>
Cc: gdb-patches@sources.redhat.com,  binutils@sources.redhat.com
Subject: Re: [RFC]: patch #2 for Sun C compiled target programs
Date: Mon, 21 Jun 2004 15:05:00 -0000	[thread overview]
Message-ID: <40D6F901.3010008@kay-mueller.de> (raw)
In-Reply-To: <200406182159.i5ILxF9G001540@elgar.kettenis.dyndns.org>

Mark Kettenis wrote:
>    Date: Fri, 18 Jun 2004 19:21:13 +0200
>    From: Michael Mueller <m.mueller99@kay-mueller.de>
> 
>    For Sun C compiled 64 bit target programs "print localvar" does not work 
>    (PR gdb/1669).
> 
>    I verified this against these compiler versions:
> 
>       Sun C 5.5 2003/03/12
>       Forte Developer 7 C 5.4 2002/03/09
>       Sun WorkShop 6 update 2 C 5.3 2001/05/15
>       Sun WorkShop 6 2000/04/07 C 5.1
> 
> Would it be difficult for you to test with GCC too?

I tested with gcc 3.4 and found no problem.


> Sorry but that change is unacceptable.  It's an obvious hack and might
> break other targets.  It's not at all clear what values are supposed
> to be sign-extended and what values are not, as mentioned in the
> thread cited by you.

I did not expect this. Of curse it's just a hack. Sorry for the 
misunderstanding.

> 
> The real problem is that dbxread.c was initially written as 32-bit
> only code.  The sign-extension problem you're seeing here can also be
> interpreted as a 64-bit-dirty issue.

So how can it be fixed?

> 
>    *** Problem 2 *************************************************
> 
>    Function sparc64_frame_base_address in sparc64-tdep.c needs to be fixed:
> 
>       /* ??? Should we take BIAS into account here?  */
>       return cache->base;
> 
> 
>    The answer to the question in comment is yes, see the appended patch.
> 
> That sounds reasonable.  I'll commit that bit if it works with
> GCC/DWARF too.

I debugged gcc3.4/dwarf. It does not call sparc64_frame_base_address. (I 
assume dwarf uses a location expression of it's own to describe a fp 
based address + BIAS as the location of a stack variable.)


> 
> Mark
> 


  reply	other threads:[~2004-06-21 15:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-18 17:21 Michael Mueller
2004-06-18 21:59 ` Mark Kettenis
2004-06-21 15:05   ` Michael Mueller [this message]
2004-06-24 19:34     ` Mark Kettenis
2004-06-24 19:47     ` Mark Kettenis
2004-06-24 20:57       ` Michael Mueller
2004-06-28  8:16       ` Michael Mueller

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=40D6F901.3010008@kay-mueller.de \
    --to=m.mueller99@kay-mueller.de \
    --cc=binutils@sources.redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=kettenis@chello.nl \
    /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