From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: gdb-patches@sourceware.org
Subject: sigthread.exp
Date: Sun, 28 Jan 2007 14:35:00 -0000 [thread overview]
Message-ID: <200701281435.l0SEZLrx027406@brahms.sibelius.xs4all.nl> (raw)
This test is a bit fragile, since it depends on timing of some
operations. On OpenBSD, 1000000 iterations isn't enough, but
increasing it by a factor 10 does the trick.
ok?
Index: ChangeLog
from Mark Kettenis <kettenis@gnu.org>
* gdb.threads/sigthread.c (NSIGS): Make bigger.
Index: gdb.threads/sigthread.c
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.threads/sigthread.c,v
retrieving revision 1.1
diff -u -p -r1.1 sigthread.c
--- gdb.threads/sigthread.c 8 Jan 2007 21:09:47 -0000 1.1
+++ gdb.threads/sigthread.c 28 Jan 2007 14:30:49 -0000
@@ -18,7 +18,7 @@
/* Loop long enough for GDB to send a few signals of its own, but
don't hang around eating CPU forever if something goes wrong during
testing. */
-#define NSIGS 1000000
+#define NSIGS 10000000
void
handler (int sig)
next reply other threads:[~2007-01-28 14:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-28 14:35 Mark Kettenis [this message]
2007-01-28 14:43 ` sigthread.exp 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=200701281435.l0SEZLrx027406@brahms.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--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