From: Pedro Alves <palves@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: gdb-7.8 branching status (2014-06-04)
Date: Thu, 05 Jun 2014 13:58:00 -0000 [thread overview]
Message-ID: <5390778C.3020206@redhat.com> (raw)
In-Reply-To: <20140604182038.GX4289@adacore.com>
On 06/04/2014 07:20 PM, Joel Brobecker wrote:
>> I also filed PRs for the gdbserver regressions I had mentioned before.
>>
>> [Bug go/17018] New: XFAIL: gdb.go/hello.exp: Starting string check
>> https://sourceware.org/PR17018
>>
>> [Bug gdb/17019] New: gdb.base/restore.exp failures
>> https://sourceware.org/PR17019
>>
>> [Bug gdb/17020] New: gdb.base/store.exp failures
>> https://sourceware.org/PR17020
>>
>> [Bug gdb/17016] New: XFAIL: gdb.threads/dlopen-libpthread.exp: info probes all rtld rtld_map_complete
>> https://sourceware.org/PR17016
>>
>> [Bug gdb/17015] New: gdb.trace/collection.exp failures
>> https://sourceware.org/PR17015
>>
>> [Bug gdb/17014] New: gdb.trace/unavailable.exp failures
>> https://sourceware.org/PR17014
>>
>> Likely most of those are system/gcc related though. I'm diffing
>> against a gdb.sum from a month ago, and I updated my Fedora in
>> the mean time... Still, it's shame that all these are failing
>> on newer systems.
>>
>> I'll run the testsuite on my current system against 7.7,
>> diff the result against mainline, and update the PRs with
>> what I find out. If they fail on 7.7 as well, they're not
>> regressions, so can't be blockers.
>
> Thanks for doing that, Pedro. Let us know when you have the results,
> so we know whether we're in the clear or not...
I've done this now. I had to rerun all testing in non-parallel mode
to get good diffs...
The "good" news, I get all those FAILs with 7.7 too, so not
regressions.
Apart from the break-interp-exp crashes Markus has a fix for, and
a few PASS -> XFAIL that are marked as GCC bugs, I saw this
with both native and gdbserver:
-PASS: gdb.cp/koenig.exp: p entry (c)
+FAIL: gdb.cp/koenig.exp: p entry (c)
This is:
Regression for gdb.cp/koenig.exp: p entry (c) [Re: [RFA] Fix c++/16253 (tag/variable name collision)]
https://sourceware.org/ml/gdb-patches/2014-04/msg00374.html
I don't know the current status of that one. Keith?
and this one on native:
-PASS: gdb.base/pie-execl.exp: continue
-PASS: gdb.base/pie-execl.exp: pie_execl_marker address second
-PASS: gdb.base/pie-execl.exp: pie_execl_marker address has changed
+ERROR: Process no longer exists
+UNRESOLVED: gdb.base/pie-execl.exp: continue
I looked at the backtrace and it's the same as with the
break-interp.exp crashes, so it'll likely be fixed with
Markus' patch.
--
Pedro Alves
next prev parent reply other threads:[~2014-06-05 13:58 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-04 17:18 Joel Brobecker
2014-06-04 17:35 ` Pedro Alves
2014-06-04 17:46 ` Joel Brobecker
2014-06-04 17:54 ` Pedro Alves
2014-06-04 17:58 ` Pedro Alves
2014-06-04 18:17 ` [RFA] gdbserver crash if the_target->supports_z_point_type is NULL Joel Brobecker
2014-06-04 20:09 ` Pedro Alves
2014-06-04 22:21 ` pushed: " Joel Brobecker
2014-06-04 18:20 ` gdb-7.8 branching status (2014-06-04) Joel Brobecker
2014-06-05 13:58 ` Pedro Alves [this message]
2014-06-05 14:15 ` Keith Seitz
2014-06-05 14:39 ` Keith Seitz
2014-06-05 21:49 ` Joel Brobecker
2014-06-04 18:41 ` Keith Seitz
2014-06-04 22:23 ` Joel Brobecker
2014-06-05 17:26 ` Doug Evans
2014-06-04 23:03 ` Joel Brobecker
2014-06-05 21:03 ` Joel Brobecker
2014-06-06 16:30 ` Pedro Alves
2014-06-05 21:47 ` Joel Brobecker
2014-06-05 14:40 ` Yao Qi
2014-06-05 16:07 ` Pedro Alves
2014-06-05 21:50 ` Joel Brobecker
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=5390778C.3020206@redhat.com \
--to=palves@redhat.com \
--cc=brobecker@adacore.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