public inbox for frysk-bugzilla@sourceware.org help / color / mirror / Atom feed
From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org> To: frysk-bugzilla@sourceware.org Subject: [Bug general/3997] SIGTRAP handler gets reset when single stepping Date: Fri, 09 Mar 2007 10:42:00 -0000 [thread overview] Message-ID: <20070309104207.23414.qmail@sourceware.org> (raw) In-Reply-To: <20070207161918.3997.mark@klomp.org> ------- Additional Comments From mark at klomp dot org 2007-03-09 10:42 ------- According to a comment by roland on https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=227693 this isn't a bug, but expected behaviour of ptrace single stepping into sig trap handler (so, I assume it was a bug that this worked on older kernels). Since stepping into a sig trap handler will produce a sig trap signal itself (because that is how ptrace reports the single step action) and the kernel cannot rely on there being a debugger/parent swallowing that second sig trap signal. Note that single stepping into any other signal handler doesn't have this problem. So we will have to come up with a trick to (simulate?) single stepping into a sig trap handler. Leaving this open for now. -- What |Removed |Added ---------------------------------------------------------------------------- Status|SUSPENDED |NEW http://sourceware.org/bugzilla/show_bug.cgi?id=3997 ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
next prev parent reply other threads:[~2007-03-09 10:42 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-02-07 16:19 [Bug general/3997] New: " mark at klomp dot org 2007-02-07 16:51 ` [Bug general/3997] " mark at klomp dot org 2007-02-09 21:36 ` mark at klomp dot org 2007-02-10 0:22 ` cagney at redhat dot com 2007-03-06 18:50 ` mark at klomp dot org 2007-03-07 17:34 ` cmoller at redhat dot com 2007-03-09 10:42 ` mark at klomp dot org [this message] 2007-03-19 12:00 ` mark at klomp dot 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=20070309104207.23414.qmail@sourceware.org \ --to=sourceware-bugzilla@sourceware.org \ --cc=frysk-bugzilla@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: linkBe 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).