Summary: | Stepping + no debuginfo == bad news | ||
---|---|---|---|
Product: | frysk | Reporter: | Mike Cvet <mcvet> |
Component: | general | Assignee: | Mike Cvet <mcvet> |
Status: | ASSIGNED --- | ||
Severity: | normal | ||
Priority: | P2 | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Host: | Target: | ||
Build: | Last reconfirmed: | ||
Bug Depends on: | |||
Bug Blocks: | 1633, 3346 |
Description
Mike Cvet
2006-11-23 15:35:19 UTC
frysk-core/frysk/rt: 2006-11-23 Mike Cvet <mcvet@redhat.com> * RunState.java (setUpStep): If the DwflLine returned is null, perform an instruction step. Handles line stepping within frames without debug info. Temporary fix for #3575. * StackFrame.java (frameToString): Renamed from toString(). Something to keep in mind is the case of a signal delivery, and the handler being located in a section of code with debuginfo. That being the case, the stack would be: [debuginfo code - local singal handler] [non-debuginfo code - signal stuff] [debuginfo code - rest of program] The user may not necessarily want to skip over the handler, even though the signal delivery code is a non-debuginfo section. i Another possibility is to just require a breakpoint set on handler code if that is the area of interest. |