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/4383] New: needsSuspendedAction Observation support needs rewriting Date: Tue, 17 Apr 2007 11:01:00 -0000 [thread overview] Message-ID: <20070417120057.4383.mark@klomp.org> (raw) For inserting and deletion of breakpoints a mechanism was added to Observation to request suspension of the Proc before taking the actual action. There are 2 flaws with this mechanism. One in the design and one in the implementation. The design is slightly wrong since it is currently checked at the Task level, but should be checked at the Proc level and passed down to the Task level when the Proc is in the right state. The implementation for PtraceTask uses SIGSTOP, but takes action when a StoppedEvent is attempted, NOT when the Task (which should be Proc, are rather all the Tasks of a Proc, see above) is actually in the stopped state. All Tasks of the Proc should be in the T (Z or X) state. Which can be achieved by actually delivering the SIGSTOP or explicitly iterating over all the Task and get them into traced (or stopped, zombie or dead) state. -- Summary: needsSuspendedAction Observation support needs rewriting Product: frysk Version: unspecified Status: NEW Severity: normal Priority: P2 Component: general AssignedTo: frysk-bugzilla at sourceware dot org ReportedBy: mark at klomp dot org http://sourceware.org/bugzilla/show_bug.cgi?id=4383 ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
reply other threads:[~2007-04-17 11:01 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20070417120057.4383.mark@klomp.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).