From: Andrew Cagney <ac131313@cygnus.com>
To: "Martin M. Hunt" <hunt@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] shared library address patch
Date: Mon, 19 Feb 2001 16:48:00 -0000 [thread overview]
Message-ID: <3A91BE58.665C6ADE@cygnus.com> (raw)
In-Reply-To: <Pine.SUN.4.33.0102191527540.2670-100000@rtl.cygnus.com>
[I'm not the maintainer]
Once your ssh account create has been created, can you add your self to
the MAINTAINERS file under write after approval.
"Martin M. Hunt" wrote:
>
> The following patch keeps GDB from relocating shared libraries on
> mipsel-linux-gnu out of the 32-bit address space. On researching this, I
> noticed Maciej W. Rozycki proposed a similar fix back in July
> (see http://sources.redhat.com/ml/gdb-patches/2000-07/msg00260.html )
FYI, Maciej submitted a number of patches. I'm not 100% certain of
Maciej's assignment status though. This is a case of independantly
reproducing an obvious change.
Andrew
> 2001-02-19 Martin M. Hunt <hunt@redhat.com>
>
> * solib-svr4.c (LM_ADDR): LM_ADDR is a signed offset, so
> extract_signed_integer() should be called instead of
> extract_address().
>
> Index: solib-svr4.c
> ===================================================================
> RCS file: /cvs/src/src/gdb/solib-svr4.c,v
> retrieving revision 1.8
> diff -u -p -r1.8 solib-svr4.c
> --- solib-svr4.c 2001/02/08 06:03:53 1.8
> +++ solib-svr4.c 2001/02/19 23:22:25
> @@ -249,7 +249,8 @@ LM_ADDR (struct so_list *so)
> {
> struct link_map_offsets *lmo = SVR4_FETCH_LINK_MAP_OFFSETS ();
>
> - return extract_address (so->lm_info->lm + lmo->l_addr_offset, lmo->l_addr_size);
> + return (CORE_ADDR) extract_signed_integer (so->lm_info->lm + lmo->l_addr_offset,
> + lmo->l_addr_size);
> }
>
> static CORE_ADDR
next prev parent reply other threads:[~2001-02-19 16:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-19 15:33 Martin M. Hunt
2001-02-19 16:48 ` Andrew Cagney [this message]
2001-02-19 18:29 ` Kevin Buettner
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=3A91BE58.665C6ADE@cygnus.com \
--to=ac131313@cygnus.com \
--cc=gdb-patches@sources.redhat.com \
--cc=hunt@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