From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb@sourceware.org
Subject: Re: gdb-7.1 release preparation...
Date: Thu, 11 Mar 2010 21:18:00 -0000 [thread overview]
Message-ID: <20100311211808.GA2470@host0.dyn.jankratochvil.net> (raw)
In-Reply-To: <20100309181021.GI15364@adacore.com>
On Tue, 09 Mar 2010 19:10:21 +0100, Joel Brobecker wrote:
> Anything that we are still missing before we can release?
There is now on gdb_7_1-branch a regression-against-7.0 due to the PIE
patchset as bugreported by Daniel Jacobowitz:
./gdbserver/gdbserver :2222 /lib64/ld-linux-x86-64.so.2 ./gdb -nx;stty sane
+
./gdb -nx -ex 'target remote localhost:2222' -ex 'b main' -ex c ./gdb
CTRL-C
bt
It has been fixed on master by:
Re: RFC: Verify AT_ENTRY before using it
http://sourceware.org/ml/gdb-patches/2010-03/msg00395.html
thread start: http://sourceware.org/ml/gdb-patches/2010-02/msg00612.html
http://sourceware.org/ml/gdb-cvs/2010-03/msg00096.html
264e6edfb36d5c827cd0918c1c500dba983b6fca
Daniel Jacobowitz has reported also another regression due to PIE this time
for remote embedded target. Fixed on master by:
Re: PIE question
http://sourceware.org/ml/gdb/2010-03/msg00051.html
http://sourceware.org/ml/gdb-cvs/2010-03/msg00097.html
a2544b6d0024147ad7dd01fd4dad0403c761bb2f
OK to check-in also for gdb_7_1-branch?
Thanks,
Jan
next prev parent reply other threads:[~2010-03-11 21:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-09 18:10 Joel Brobecker
2010-03-09 18:22 ` Pedro Alves
2010-03-10 13:14 ` Pierre Muller
2010-03-10 17:48 ` Joel Brobecker
2010-03-11 19:46 ` Jonas Maebe
2010-03-11 20:10 ` Sérgio Durigan Júnior
2010-03-11 21:18 ` Jan Kratochvil [this message]
2010-03-12 7:57 ` Joel Brobecker
2010-03-14 4:57 ` Daniel Jacobowitz
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=20100311211808.GA2470@host0.dyn.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb@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