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 tdep/31442] New: [gdb/tdep, arm, SIGILL] FAIL: gdb.threads/sigstep-threads.exp: step 92
Date: Sat, 02 Mar 2024 12:33:19 +0000	[thread overview]
Message-ID: <bug-31442-4717@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 31442
           Summary: [gdb/tdep, arm, SIGILL] FAIL:
                    gdb.threads/sigstep-threads.exp: step 92
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: tdep
          Assignee: unassigned at sourceware dot org
          Reporter: vries at gcc dot gnu.org
  Target Milestone: ---

On arm-linux, I ran into:
...
(gdb) step^M
^M
Thread 2 "sigstep-threads" received signal SIGUSR1, User defined signal 1.^M
^M
Thread 2 "sigstep-threads" received signal SIGILL, Illegal instruction.^M
[Switching to Thread 0xf76a5420 (LWP 2340)]^M
0xaaaaa5e4 in handler (signo=10) at
/home/rock/gdb/src/gdb/testsuite/gdb.threads/sigstep-threads.c:32^M
32        var++;                /* step-1 */^M
(gdb) FAIL: gdb.threads/sigstep-threads.exp: step 92
...

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

             reply	other threads:[~2024-03-02 12:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-02 12:33 vries at gcc dot gnu.org [this message]
2024-03-03 11:01 ` [Bug tdep/31442] " vries at gcc dot gnu.org
2024-03-05 16:41 ` [Bug external/31442] [gdb/external, " 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-31442-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).