public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug threads/26228] New: FAIL: gdb.threads/create-fail.exp: iteration x: run till end (SIG32)
Date: Sat, 11 Jul 2020 08:35:07 +0000 [thread overview]
Message-ID: <bug-26228-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=26228
Bug ID: 26228
Summary: FAIL: gdb.threads/create-fail.exp: iteration x: run
till end (SIG32)
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: threads
Assignee: unassigned at sourceware dot org
Reporter: vries at gcc dot gnu.org
Target Milestone: ---
Here ( https://sourceware.org/pipermail/gdb-testers/2020q3/169745.html ) we
find in gdb.sum:
...
FAIL: gdb.threads/create-fail.exp: iteration 10: run till end
FAIL: gdb.threads/create-fail.exp: iteration 1: run till end
FAIL: gdb.threads/create-fail.exp: iteration 2: run till end
FAIL: gdb.threads/create-fail.exp: iteration 3: run till end
FAIL: gdb.threads/create-fail.exp: iteration 4: run till end
FAIL: gdb.threads/create-fail.exp: iteration 5: run till end
FAIL: gdb.threads/create-fail.exp: iteration 6: run till end
FAIL: gdb.threads/create-fail.exp: iteration 7: run till end
FAIL: gdb.threads/create-fail.exp: iteration 8: run till end
FAIL: gdb.threads/create-fail.exp: iteration 9: run till end
...
In more detail, in gdb.log:
...
(gdb) run
Starting program:
/home/gdb-buildbot-2/fedora-x86-64-4/fedora-x86-64/build/gdb/testsuite/outputs/gdb.threads/create-fail/create-fail
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Breakpoint 1, main () at
/home/gdb-buildbot-2/fedora-x86-64-4/fedora-x86-64/build/gdb/testsuite/../../../binutils-gdb/gdb/testsuite/gdb.threads/create-fail.c:69
69 for (i = 0; i < CPU_SETSIZE; i++)
(gdb) continue
Continuing.
[New Thread 0x7ffff7c83700 (LWP 626354)]
[New Thread 0x7ffff7482700 (LWP 626355)]
[Thread 0x7ffff7c83700 (LWP 626354) exited]
[New Thread 0x7ffff6c81700 (LWP 626356)]
[Thread 0x7ffff7482700 (LWP 626355) exited]
[New Thread 0x7ffff6480700 (LWP 626357)]
[Thread 0x7ffff6c81700 (LWP 626356) exited]
[New Thread 0x7ffff5c7f700 (LWP 626358)]
[Thread 0x7ffff6480700 (LWP 626357) exited]
pthread_create: 22: Invalid argument
Thread 6 "create-fail" received signal SIG32, Real-time event 32.
[Switching to Thread 0x7ffff5c7f700 (LWP 626358)]
0x00007ffff7d87695 in clone () from /lib64/libc.so.6
(gdb) FAIL: gdb.threads/create-fail.exp: iteration 1: run till end
...
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2020-07-11 8:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-11 8:35 vries at gcc dot gnu.org [this message]
2020-07-11 8:52 ` [Bug threads/26228] " vries at gcc dot gnu.org
2020-07-11 9:11 ` vries at gcc dot gnu.org
2020-07-24 13:59 ` vries at gcc dot gnu.org
2021-02-01 21:44 ` vries at gcc dot gnu.org
2021-02-02 11:55 ` luis.machado at linaro dot org
2021-02-04 13:27 ` vries at gcc dot gnu.org
2021-02-04 14:11 ` luis.machado at linaro dot org
2021-02-04 14:15 ` vries at gcc dot gnu.org
2021-02-04 14:24 ` luis.machado at linaro dot org
2021-02-04 17:27 ` vries at gcc dot gnu.org
2021-02-12 19:12 ` cvs-commit at gcc dot gnu.org
2021-02-12 19:13 ` vries at gcc dot gnu.org
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=bug-26228-4717@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).