From: Michael Mueller <m.mueller99@kay-mueller.de>
To: Mark Kettenis <kettenis@chello.nl>
Cc: m.mueller99@kay-mueller.de, gdb-patches@sources.redhat.com
Subject: Re: [RFC]: patch #2 for Sun C compiled target programs
Date: Thu, 24 Jun 2004 20:57:00 -0000 [thread overview]
Message-ID: <40DB3FF9.6050509@kay-mueller.de> (raw)
In-Reply-To: <200406241947.i5OJlgKr017239@elgar.kettenis.dyndns.org>
Mark Kettenis wrote:
> Date: Mon, 21 Jun 2004 17:04:33 +0200
> From: Michael Mueller <m.mueller99@kay-mueller.de>
>
> >
> > 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?
>
> Not sure. As I said, it's not easy. As far as I understand things,
> INTERNALIZE_SYMBOL() should look at n_type to decide whether n_value
> should be treated as a signed or an unsigned value. The problem seems
> to be that n_value can either be interpreted as an address or as an
> offset. Addresses should be sign-extended based on what
> bfd_get_sign_extend_vma() tells us. Offsets should probably always be
> sign-extended.
>
> Mark
>
How about sign extending it a bit alter in process_one_symbol when we
find out it's a stack variable? I cannot imagine an architecture where a
stack variable has an absolute address. But my imagination is limited.
Michael
next prev parent reply other threads:[~2004-06-24 20:57 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
2004-06-24 19:34 ` Mark Kettenis
2004-06-24 19:47 ` Mark Kettenis
2004-06-24 20:57 ` Michael Mueller [this message]
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=40DB3FF9.6050509@kay-mueller.de \
--to=m.mueller99@kay-mueller.de \
--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