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/4389] ptrace in event-loop causes TestBreakpoints inferior to sig-seg-v
Date: Wed, 18 Apr 2007 11:35:00 -0000	[thread overview]
Message-ID: <20070418113456.15219.qmail@sourceware.org> (raw)
In-Reply-To: <20070417225454.4389.cagney@redhat.com>


------- Additional Comments From mark at klomp dot org  2007-04-18 12:34 -------
(In reply to comment #2)
> and it's sending PT_CONT of signal 5/SIGTRAP to the process.  Per other
> discussion, if in a signal handler this can kill the inferior.

Not in this case since the funit-breakpoints uses the SA_NODEFER workaround. The
test does check that SIGTRAP and segfaults not caused by frysk itself are
propagated correctly. See bug #3997 for a discussion about this.

I'll checkout the branch and test first against the simpler unit tests first.
TestTaskObserverCode which only does a set breakpoint, run, check that it got
hit (maybe expand it to then continue running again), the
TestTaskObserverInstruction test, the TestTaskObserverInstructionSigReturn and
the combined TestTaskObserverInstructionAndCode tests. If those work then we can
proceed with the all singing and dancing TestBreakpoints which is really a
combination of all those tests.

-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=4389

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.


  parent reply	other threads:[~2007-04-18 11:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-17 21:55 [Bug general/4389] New: " cagney at redhat dot com
2007-04-17 22:34 ` [Bug general/4389] " cagney at redhat dot com
2007-04-17 22:46 ` cagney at redhat dot com
2007-04-18 11:35 ` mark at klomp dot org [this message]
2007-04-18 12:10 ` mark at klomp dot org
2007-04-18 17:58 ` cagney at redhat dot com
2007-04-19 12:55 ` mark at klomp dot org
2007-04-19 14:21 ` cagney at redhat dot com
2007-04-19 17:03 ` cagney 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=20070418113456.15219.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: 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).