From: Daniel Jacobowitz <drow@false.org>
To: Thiago Jung Bauermann <bauerman@br.ibm.com>
Cc: Vladimir Prus <ghost@cs.msu.su>,
Greg Law <glaw@undo-software.com>,
gdb-patches@sources.redhat.com
Subject: Re: SIGSEGV on gdb 6.7*
Date: Thu, 28 Feb 2008 16:18:00 -0000 [thread overview]
Message-ID: <20080228141834.GC8988@caradoc.them.org> (raw)
In-Reply-To: <1204207961.18153.50.camel@localhost.localdomain>
On Thu, Feb 28, 2008 at 11:12:41AM -0300, Thiago Jung Bauermann wrote:
> On Thu, 2008-02-28 at 10:15 +0300, Vladimir Prus wrote:
> > This patch cause testsuite regressions for me, as follows:
> >
> > FAIL: gdb.base/annota1.exp: continue to printf
> > FAIL: gdb.base/annota1.exp: send SIGUSR1
> > FAIL: gdb.base/annota1.exp: signal sent
>
> In my experience, this testcase is "nondeterministic", meaning that it
> will go back and forth between PASS and FAIL for no good reason.
The whole testcase is not; there's a few particular subtests that are,
which involve SIGINT. We've never managed to reproduce that one
outside of expect, unfortunately.
> Is it useful to have such list on the wiki?
Sure, but with attached example logs might be best so that we can
remove them when they're fixed.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-02-28 14:18 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-04 20:50 Greg Law
2008-02-04 21:04 ` Daniel Jacobowitz
2008-02-04 21:39 ` Greg Law
[not found] ` <47A7850B.10202@undo-software.com>
2008-02-04 21:45 ` Daniel Jacobowitz
2008-02-04 21:59 ` Greg Law
2008-02-04 22:11 ` Daniel Jacobowitz
2008-02-04 22:36 ` Greg Law
2008-02-11 20:59 ` Greg Law
2008-02-26 23:00 ` Michael Snyder
2008-02-27 0:37 ` Daniel Jacobowitz
2008-02-27 0:43 ` Michael Snyder
2008-02-27 0:51 ` Daniel Jacobowitz
2008-02-27 0:54 ` Michael Snyder
2008-02-27 1:05 ` Daniel Jacobowitz
2008-02-27 1:08 ` Michael Snyder
2008-02-27 20:23 ` Greg Law
2008-02-28 7:46 ` Vladimir Prus
2008-02-28 14:17 ` Daniel Jacobowitz
2008-02-28 14:17 ` Thiago Jung Bauermann
2008-02-28 16:18 ` Daniel Jacobowitz [this message]
2008-03-04 20:09 ` 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=20080228141834.GC8988@caradoc.them.org \
--to=drow@false.org \
--cc=bauerman@br.ibm.com \
--cc=gdb-patches@sources.redhat.com \
--cc=ghost@cs.msu.su \
--cc=glaw@undo-software.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