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/5229] New: Code observer unblock right before delete request hangs Date: Mon, 29 Oct 2007 08:55:00 -0000 [thread overview] Message-ID: <20071029085508.5229.mark@klomp.org> (raw) Doing an unblock of a Code observer triggering a step over the breakpoint and immediately (before the step over the breakpoint is completed) requesting the deletion of the Code observer from that address will hang the inferior. This is most likely related to bug #4383 which explains that we send too many stop events to the inferior. I wrote a testcase frysk.proc.TestTaskObserverCode.testMultiTaskUpdateUnblockDelete that shows the problem. It can probably be simplified a little. The behaviour of the above test is slightly different between x86_64/fc6 (kernel 2.6.22.9-61.fc6) where it hangs frysk itself (!) and x86/f8 (2.6.23.1-31.fc8) where only the inferior hangs, but frysk-core seems fine (and the tests times out). -- Summary: Code observer unblock right before delete request hangs 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=5229 ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
reply other threads:[~2007-10-29 8:55 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=20071029085508.5229.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).