From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org, Jeff Johnston <jjohnstn@redhat.com>
Subject: Re: [patch 00/15] PIE: Position Independent Executable support
Date: Sun, 10 Jan 2010 20:25:00 -0000 [thread overview]
Message-ID: <20100110202448.GL10482@host0.dyn.jankratochvil.net> (raw)
In-Reply-To: <m37htycnrd.fsf@fleche.redhat.com>
On Tue, 10 Nov 2009 18:07:02 +0100, Tom Tromey wrote:
> >>>>> "Jan" == Jan Kratochvil <jan.kratochvil@redhat.com> writes:
>
> Jan> The patchset does not introduce nothing much new and it is more a
> Jan> general set of miscellaneous fixes merged together to make a
> Jan> special inferior case of PIE working. At least some of the small
> Jan> fixes should be easy to get accepted.
>
> I think this patch should have a NEWS entry.
Sure only after the patchset gets checked-in.
Thanks,
Jan
2010-01-10 Jan Kratochvil <jan.kratochvil@redhat.com>
* NEWS: Document the PIE support.
--- a/gdb/NEWS
+++ b/gdb/NEWS
@@ -184,6 +184,10 @@ much more reliable. In particular:
- GDB is now able to backtrace through the signal handler for
non-threaded programs.
+PIE (Position Independent Executable) programs debugging is now supported.
+This includes debugging execution of PIC (Position Independent Code) shared
+libraries although such libraries must first support their execution.
+
*** Changes in GDB 7.0
* GDB now has an interface for JIT compilation. Applications that
next prev parent reply other threads:[~2010-01-10 20:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-09 20:56 Jan Kratochvil
2009-11-10 17:07 ` Tom Tromey
2010-01-10 20:25 ` Jan Kratochvil [this message]
2010-01-10 22:02 ` Eli Zaretskii
2010-01-10 22:27 ` Jan Kratochvil
2010-01-11 4:09 ` Eli Zaretskii
2010-01-11 14:45 ` Jan Kratochvil
2010-01-14 21:25 ` Jan Kratochvil
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=20100110202448.GL10482@host0.dyn.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jjohnstn@redhat.com \
--cc=tromey@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