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: Mon, 19 Mar 2007 12:00:00 -0000 [thread overview] Message-ID: <20070319120014.21483.qmail@sourceware.org> (raw) In-Reply-To: <20070207161918.3997.mark@klomp.org> ------- Additional Comments From mark at klomp dot org 2007-03-19 12:00 ------- This is a misfeature of ptrace single step. It uses SIGTRAP to signal that a step is made. this used to work in older kernels. But newer kernels decided to block the sig trap handler if the child wasn't using a reentrant sigtrap handler (even though the ptracing debugger would of course swallow the signal and never deliver it to the child itself). Resetting the child signal handler obviously breaks out testcases. For now, to have minimal testing of sigtrap handler stepping, we instrument the test programs to us SA_NODEFER. Also the funit-breakpoints uses a simple SIGUSER handler to test signal stepping and breakpointing. The real solution for this problem, so we can single step also non-altered user programs that use SIGTRAP, is to use a, non-existing yet, interface on top of utrace that doesn't use SIGTRAP for reporting events to frysk. -- 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.
prev parent reply other threads:[~2007-03-19 12:00 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 2007-03-19 12:00 ` mark at klomp dot org [this message]
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=20070319120014.21483.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).