From: Doug Evans <dje@google.com>
To: Patrick Palka <patrick@parcs.ath.cx>
Cc: Joel Brobecker <brobecker@adacore.com>,
gdb-patches <gdb-patches@sourceware.org>
Subject: Re: Several regressions and we branch soon.
Date: Tue, 23 Jun 2015 19:03:00 -0000 [thread overview]
Message-ID: <CADPb22Rg2FySdxWo9VKb5WApPh-wdf946po9UXX-+kQ99bULug@mail.gmail.com> (raw)
In-Reply-To: <CA+C-WL_uZdNj29-6u4MnqH-8zQt9Q20fzUb6b9nWHKJPCstY9A@mail.gmail.com>
On Tue, Jun 23, 2015 at 1:55 PM, Patrick Palka <patrick@parcs.ath.cx> wrote:
> On Tue, Jun 23, 2015 at 2:31 PM, Doug Evans <dje@google.com> wrote:
>> Hi.
>>
>> fyi, I'm seeing regressions in the following tests on amd64-linux.
>>
>> FAIL: gdb.threads/attach-stopped.exp: nonthreaded: attach2 to stopped bt
>> FAIL: gdb.threads/attach-stopped.exp: threaded: attach2 to stopped bt
>> FAIL: gdb.base/attach-pie-noexec.exp: attach
>> FAIL: gdb.base/attach-pie-noexec.exp: info shared
>> FAIL: gdb.base/attach-twice.exp: attach
>> FAIL: gdb.base/attach.exp: attach1, after setting file
>> FAIL: gdb.base/attach.exp: attach1 detach (the program is no longer running)
>> FAIL: gdb.base/attach.exp: attach2, with no file
>> FAIL: gdb.base/attach.exp: after attach2, set should_exit
>> FAIL: gdb.base/attach.exp: continue to breakpoint: postloop (the
>> program is no longer running)
>> FAIL: gdb.base/attach.exp: continue until exit at after attach2, exit
>> (the program is no longer running)
>> FAIL: gdb.base/attach.exp: attach when process' a.out not in cwd
>> FAIL: gdb.base/attach.exp: continue until exit (the program is no
>> longer running)
>> FAIL: gdb.base/attach.exp: starting with --pid (timeout)
>> FAIL: gdb.base/attach.exp: cmdline attach run: run to prompt
>> UNRESOLVED: gdb.base/attach.exp: cmdline attach run: run to main
>> FAIL: gdb.base/break-interp.exp: LDprelinkNOdebugNO:
>> BINprelinkNOdebugNOpieNO: attach: attach main bt
>> FAIL: gdb.base/break-interp.exp: LDprelinkNOdebugNO:
>> BINprelinkNOdebugNOpieYES: attach: seen displacement message as
>> NONZERO
>> ... plus lots more for break-interp.exp ...
>> FAIL: gdb.base/default.exp: info set
>> FAIL: gdb.base/default.exp: show
>> FAIL: gdb.base/dprintf-detach.exp: bai=on ds=gdb dd=on: re-attach to inferior
>> FAIL: gdb.base/dprintf-detach.exp: bai=on ds=gdb dd=off: re-attach to inferior
>> FAIL: gdb.base/dprintf-detach.exp: bai=on ds=call dd=on: re-attach to inferior
>> FAIL: gdb.base/dprintf-detach.exp: bai=on ds=call dd=off: re-attach to inferior
>> FAIL: gdb.base/dprintf-detach.exp: bai=on ds=agent dd=on: re-attach to inferior
>> FAIL: gdb.base/dprintf-detach.exp: bai=on ds=agent dd=off: re-attach to inferior
>> FAIL: gdb.base/dprintf-detach.exp: bai=off ds=gdb dd=on: re-attach to inferior
>> FAIL: gdb.base/dprintf-detach.exp: bai=off ds=gdb dd=off: re-attach to inferior
>> FAIL: gdb.base/dprintf-detach.exp: bai=off ds=call dd=on: re-attach to inferior
>> FAIL: gdb.base/dprintf-detach.exp: bai=off ds=call dd=off: re-attach to inferior
>> FAIL: gdb.base/dprintf-detach.exp: bai=off ds=agent dd=on: re-attach to inferior
>> FAIL: gdb.base/dprintf-detach.exp: bai=off ds=agent dd=off: re-attach
>> to inferior
>> FAIL: gdb.base/gnu_vector.exp: call add_singlevecs
>> FAIL: gdb.base/gnu_vector.exp: continue to add_some_intvecs
>> FAIL: gdb.base/gnu_vector.exp: continue to add_some_intvecs (the
>> program is no longer running)
>> FAIL: gdb.base/gnu_vector.exp: set vector return value
>> FAIL: gdb.multi/multi-attach.exp: backtrace 1
>> FAIL: gdb.multi/multi-attach.exp: backtrace 2
>> FAIL: gdb.python/py-sync-interp.exp: attach and where
>> FAIL: gdb.server/ext-attach.exp: backtrace 1
>> FAIL: gdb.server/ext-attach.exp: detach (the program is no longer running)
>> FAIL: gdb.server/ext-attach.exp: backtrace 2
>> FAIL: gdb.server/ext-attach.exp: monitor exit
>> FAIL: gdb.threads/attach-into-signal.exp: nonthreaded: detach (the
>> program is no longer running)
>> UNRESOLVED: gdb.threads/attach-into-signal.exp: nonthreaded: attach
>> (pass 1), pending signal catch
>> FAIL: gdb.threads/attach-into-signal.exp: threaded: thread apply 2
>> print $_siginfo.si_signo
>> FAIL: gdb.threads/attach-into-signal.exp: threaded: detach (the
>> program is no longer running)
>> UNRESOLVED: gdb.threads/attach-into-signal.exp: threaded: attach (pass
>> 1), pending signal catch
>>
>> I haven't root-caused any of them yet.
>> Is anyone else seeing these on amd64-linux?
>
> GDB has not been clean of FAILs for a while right? IIRC I've been
> seeing dozens of FAILs since I started submitting patches to GDB
> (around June 2014). So I wonder how many of these are long-standing
> FAILs not introduced in this development cycle.
GDB has not been clean "since forever".
However, my testing harness takes that into account.
I have lists of tests I expect to see fail for each of my test configs
(fission, no-fission, and so on), and my harness post-processes
gdb.sum to produce a better report of pass/fail.
(using a version of validate_failures.py from gcc)
When something shows up that I haven't seen before,
and I run these tests A LOT, I can tell.
Every one of the above is new(ish - at least new in the
last few months - I've been sidelined for a few reasons
and haven't been running the tests as often as I normally do).
next prev parent reply other threads:[~2015-06-23 19:03 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-23 18:31 Doug Evans
2015-06-23 18:55 ` Patrick Palka
2015-06-23 19:03 ` Doug Evans [this message]
2015-06-23 20:17 ` Keith Seitz
2015-06-23 20:53 ` Doug Evans
2015-06-23 21:45 ` Patrick Palka
2015-06-24 11:55 ` Yao Qi
2015-06-25 16:35 ` Tedeschi, Walfred
2015-07-01 8:49 ` Yao Qi
[not found] ` <AC542571535E904D8E8ADAE745D60B1944445D44@IRSMSX104.ger.corp.intel.com>
2015-07-01 9:30 ` Walfred Tedeschi
2015-07-02 10:09 ` Yao Qi
2015-07-02 15:34 ` Yao Qi
2015-07-02 16:19 ` [PATCH] Don't throw an error in "show mpx bound" implementation Patrick Palka
2015-07-06 9:31 ` Yao Qi
2015-06-24 10:21 ` Several regressions and we branch soon Yao Qi
2015-06-25 8:21 ` Andreas Arnez
2015-06-25 13:34 ` Doug Evans
2015-06-25 18:00 ` Andreas Arnez
2015-06-30 15:21 ` Yao Qi
2015-06-30 18:09 ` Andreas Arnez
2015-07-01 8:01 ` Yao Qi
2015-07-10 9:33 ` Yao Qi
2015-07-10 16:12 ` Andreas Arnez
2015-07-10 16:23 ` Ulrich Weigand
2015-07-20 15:08 ` Andreas Arnez
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=CADPb22Rg2FySdxWo9VKb5WApPh-wdf946po9UXX-+kQ99bULug@mail.gmail.com \
--to=dje@google.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=patrick@parcs.ath.cx \
/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).