From: Matthew Fortune <Matthew.Fortune@imgtec.com>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Cc: Joseph Myers <joseph@codesourcery.com>
Subject: RE: [PATCH, MIPS] Support shared library debug with MIPS PIE (gdb)
Date: Mon, 13 Jul 2015 10:21:00 -0000 [thread overview]
Message-ID: <6D39441BF12EF246A7ABCE6654B02353211CB116@LEMAIL01.le.imgtec.org> (raw)
In-Reply-To: <alpine.DEB.2.10.1506231529530.4489@digraph.polyomino.org.uk>
Matthew Fortune <Matthew.Fortune@imgtec.com> writes:
> This tag allows debugging of MIPS position independent executables and
> provides access to shared library information.
>
> gdb/gdbserver/
>
> * linux-low.c (get_r_debug): Handle DT_MIPS_RLD_MAP_REL.
>
> gdb/
>
> * solib-svr4.c (read_program_header): Add base_addr argument to
> report the runtime address of the segment.
> (find_program_interpreter): Update read_program_header call to pass
> a NULL pointer for the new argument.
> (scan_dyntag): Add ptr_addr argument to report the runtime address
> of the tag payload.
> (scan_dyntag_auxv): Likewise and use thew new base_addr argument of
> read_program_header to get the base address of the dynamic segment.
> (elf_locate_base): Update uses of scan_dyntag, scan_dyntag_auxv and
> read_program_header.
> (elf_locate_base): Scan for and handle DT_MIPS_RLD_MAP_REL.
Ping.
Matthew
prev parent reply other threads:[~2015-07-13 10:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-23 15:23 Matthew Fortune
2015-06-23 15:31 ` Joseph Myers
2015-06-23 15:52 ` Matthew Fortune
2015-06-26 12:45 ` Matthew Fortune
2015-08-12 10:30 ` Pedro Alves
2015-08-12 13:43 ` Matthew Fortune
2015-08-12 13:59 ` Pedro Alves
2015-07-13 10:21 ` Matthew Fortune [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=6D39441BF12EF246A7ABCE6654B02353211CB116@LEMAIL01.le.imgtec.org \
--to=matthew.fortune@imgtec.com \
--cc=gdb-patches@sourceware.org \
--cc=joseph@codesourcery.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).