Bug 3564 - single-step when pending signal, and on a breakpoint instruction
Summary: single-step when pending signal, and on a breakpoint instruction
Status: NEW
Alias: None
Product: frysk
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
: P2 normal
Target Milestone: ---
Assignee: Unassigned
URL:
Keywords:
Depends on:
Blocks: 1521
  Show dependency tree / graph
 
Reported: 2006-11-22 17:27 UTC by Andrew Cagney
Modified: 2007-02-13 13:39 UTC (History)
0 users

See Also:
Host:
Target:
Build:
Last reconfirmed:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Andrew Cagney 2006-11-22 17:27:08 UTC 
This is easier than it looks, breakpoints do not need to be removed (but doing
so doesn't hurt) as the step will always go to the handler.
Comment 1 Mark Wielaard 2007-02-13 13:39:42 UTC 
This is an interesting case. The TaskState mechanism is currently not setup to
preventively remove any breakpoints. Is there any mechanism to definitely know
that a Task has any pending signals? I assume that a signal could become pending
during the next ptrace-step and if so the step ends up in the signal frame.