public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "simon.marchi at polymtl dot ca" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/31293] New: gdb.threads/threadcrash.exp failure
Date: Thu, 25 Jan 2024 12:44:26 +0000	[thread overview]
Message-ID: <bug-31293-4717@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=31293

            Bug ID: 31293
           Summary: gdb.threads/threadcrash.exp failure
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: gdb
          Assignee: unassigned at sourceware dot org
          Reporter: simon.marchi at polymtl dot ca
  Target Milestone: ---

This is a failure in a new test.  On Debian 12:

$ make check TESTS="gdb.threads/threadcrash.exp"
FAIL: gdb.threads/threadcrash.exp: test_live_inferior: thread apply 7 backtrace
FAIL: gdb.threads/threadcrash.exp: test_live_inferior: thread apply 6 backtrace
FAIL: gdb.threads/threadcrash.exp: test_live_inferior: thread apply 4 backtrace
FAIL: gdb.threads/threadcrash.exp: test_live_inferior: thread apply 3 backtrace
FAIL: gdb.threads/threadcrash.exp: test_corefile: thread apply 7 backtrace
FAIL: gdb.threads/threadcrash.exp: test_corefile: thread apply 5 backtrace
FAIL: gdb.threads/threadcrash.exp: test_corefile: thread apply 3 backtrace
FAIL: gdb.threads/threadcrash.exp: test_corefile: thread apply 2 backtrace
FAIL: gdb.threads/threadcrash.exp: test_gcore: thread apply 7 backtrace
FAIL: gdb.threads/threadcrash.exp: test_gcore: thread apply 6 backtrace
FAIL: gdb.threads/threadcrash.exp: test_gcore: thread apply 4 backtrace
FAIL: gdb.threads/threadcrash.exp: test_gcore: thread apply 3 backtrace

the first failure looks like:

thread apply 7 backtrace

Thread 7 (Thread 0x7ffff55c06c0 (LWP 1900077) "threadcrash"):
#0  0x00007ffff7e98385 in clock_nanosleep () from
/lib/x86_64-linux-gnu/libc.so.6
#1  0x00007ffff7e9cc93 in nanosleep () from /lib/x86_64-linux-gnu/libc.so.6
#2  0x00007ffff7e9cbca in sleep () from /lib/x86_64-linux-gnu/libc.so.6
#3  0x00005555555553c1 in do_syscall_task (location=SIGNAL_ALT_STACK) at
/home/smarchi/src/binutils-gdb/gdb/testsuite/gdb.threads/threadcrash.c:158
#4  0x0000555555555536 in signal_handler (signo=12) at
/home/smarchi/src/binutils-gdb/gdb/testsuite/gdb.threads/threadcrash.c:245
#5  <signal handler called>
#6  0x00007ffff7e53d3c in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#7  0x00005555555556f8 in thread_function (arg=0x5555555592f0) at
/home/smarchi/src/binutils-gdb/gdb/testsuite/gdb.threads/threadcrash.c:326
#8  0x00007ffff7e52044 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#9  0x00007ffff7ed261c in ?? () from /lib/x86_64-linux-gnu/libc.so.6
(gdb) FAIL: gdb.threads/threadcrash.exp: test_live_inferior: thread apply 7
backtrace

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2024-01-25 12:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-25 12:44 simon.marchi at polymtl dot ca [this message]
2024-01-25 12:44 ` [Bug gdb/31293] " simon.marchi at polymtl dot ca
2024-01-25 12:57 ` blarsen at redhat dot com
2024-03-05  7:30 ` [Bug testsuite/31293] " vries at gcc dot gnu.org
2024-03-11  9:57 ` cvs-commit at gcc dot gnu.org
2024-03-11  9:59 ` 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-31293-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).