From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Daniel Jacobowitz <dan@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: RFC: Verify AT_ENTRY before using it
Date: Sun, 14 Mar 2010 09:00:00 -0000 [thread overview]
Message-ID: <20100314090003.GB30789@host0.dyn.jankratochvil.net> (raw)
In-Reply-To: <20100312153852.GE9310@caradoc.them.org>
On Fri, 12 Mar 2010 16:38:52 +0100, Daniel Jacobowitz wrote:
> On Fri, Mar 12, 2010 at 04:28:31PM +0100, Jan Kratochvil wrote:
> > Is it OK also for gdb_7_1-branch?
>
> IMO yes.
Checked-in for gdb_7_1-branch:
http://sourceware.org/ml/gdb-cvs/2010-03/msg00123.html
2010-03-14 Jan Kratochvil <jan.kratochvil@redhat.com>
Daniel Jacobowitz <dan@codesourcery.com>
* solib-svr4.c (read_program_header): Support type == -1 to read
all program headers.
(read_program_headers_from_bfd): New function.
(svr4_static_exec_displacement): Remove and move the comment ...
(svr4_exec_displacement): ... here. Remove variable found. New
variable displacement. Check also DYNAMIC. Verify DISPLACEMENT
alignment for ELF targets. Compare target vs. exec_bfd PHDRs for ELF
targets using read_program_headers_from_bfd. Remove the call of
svr4_static_exec_displacement.
Thanks,
Jan
prev parent reply other threads:[~2010-03-14 9:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-24 22:49 Daniel Jacobowitz
2010-02-25 22:16 ` Jan Kratochvil
2010-02-26 21:12 ` Daniel Jacobowitz
2010-03-01 20:04 ` Jan Kratochvil
2010-03-01 21:22 ` [patch-testcase] " Jan Kratochvil
2010-03-08 22:13 ` Daniel Jacobowitz
2010-03-11 21:54 ` Jan Kratochvil
2010-03-11 21:57 ` Daniel Jacobowitz
2010-03-11 22:07 ` Jan Kratochvil
2010-03-08 22:06 ` Daniel Jacobowitz
2010-03-10 21:11 ` Jan Kratochvil
2010-03-10 21:55 ` Daniel Jacobowitz
2010-03-12 15:28 ` Jan Kratochvil
2010-03-12 15:39 ` Daniel Jacobowitz
2010-03-14 9:00 ` Jan Kratochvil [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=20100314090003.GB30789@host0.dyn.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=dan@codesourcery.com \
--cc=gdb-patches@sourceware.org \
/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