public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "palves at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/17511] Program received signal SIGTRAP, after step to signal handler -> step inside handler -> continue
Date: Sun, 26 Oct 2014 22:18:00 -0000 [thread overview]
Message-ID: <bug-17511-4717-w7Qer1MdkP@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-17511-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=17511
--- Comment #1 from Pedro Alves <palves at redhat dot com> ---
This is a kernel bug. I've reported it to Oleg Nesterov, and he pointed me at:
http://marc.info/?t=127550678000005
The first message has a ptrace-only test-case.
I'm extending gdb.base/sigstep.exp to cover this, xfailed.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2014-10-26 22:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-26 22:15 [Bug gdb/17511] New: " palves at redhat dot com
2014-10-26 22:18 ` palves at redhat dot com [this message]
2014-10-28 15:52 ` [Bug gdb/17511] " cvs-commit at gcc dot gnu.org
2014-11-07 15:40 ` cvs-commit at gcc dot gnu.org
2014-12-25 0:46 ` cvs-commit at gcc dot gnu.org
2015-02-28 16:05 ` palves at redhat dot com
2015-03-01 5:22 ` palves at redhat dot com
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-17511-4717-w7Qer1MdkP@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).