Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Kevin Buettner <kevinb@redhat.com>
To: TAKAI Kousuke <takai@vlsi.kuee.kyoto-u.ac.jp>,
	gdb-patches@sources.redhat.com
Subject: Re: [PATCH] fix solib-svr4.c with 64-bit bfd
Date: Thu, 17 Jan 2002 11:47:00 -0000	[thread overview]
Message-ID: <1020117194557.ZM11189@localhost.localdomain> (raw)
In-Reply-To: TAKAI Kousuke <takai@vlsi.kuee.kyoto-u.ac.jp> "[PATCH] fix solib-svr4.c with 64-bit bfd" (Jan 18,  4:26am)

On Jan 18,  4:26am, TAKAI Kousuke wrote:

> I had encountered a bug in GDB 5.1 compiled for sparc-sun-solaris2.8,
> that GDB cannot resolve symbols in shared libraries in 32-bit environment.
> (I found this problem had been reported as PR gdb/266).
> 
> I found that this seems to be because LM_ADDR() in solib-svr4.c
> sign-extends 32-bit address value into 64-bit CORE_ADDR type.
> I have no access to SVR4 spec, but under SunOS 5.7 and 5.8,
> <sys/link.h> says that `l_addr' is unsigned, and it seems that
> l_addr should be zero-extended.
> 
> This is a patch to fix it.
[...]

Thanks for your patch.

While your patch fixes the problems that you're seeing on Solaris, it
breaks GDB on certain other platforms.  In fact, your patch simply
reverts a change that was made last year to "fix" GDB on one of these
other platforms.  I discuss this matter more fully in

    http://sources.redhat.com/ml/gdb/2001-10/msg00036.html

I'll be revisiting this matter in a couple of weeks and will fix it
properly then.  (The changes are a bit involved.)

Thanks again,

Kevin


      reply	other threads:[~2002-01-17 19:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-17 11:26 TAKAI Kousuke
2002-01-17 11:47 ` Kevin Buettner [this message]

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=1020117194557.ZM11189@localhost.localdomain \
    --to=kevinb@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=takai@vlsi.kuee.kyoto-u.ac.jp \
    /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