[Bug python/16186] New: unwinding API should be per-thread

[Bug python/16186] New: unwinding API should be per-thread

[tromey at redhat dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=16186

            Bug ID: 16186
           Summary: unwinding API should be per-thread
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: python
          Assignee: unassigned at sourceware dot org
          Reporter: tromey at redhat dot com

Right now one can only really unwind the selected
thread from Python.  This is a bit of an ugly API.
However, nothing prevents us from improving it.

I think gdb.Thread should have a "newest_frame" method.
Then a Frame should probably refer to the thread
from which it came.  gdb could select this thread temporarily
in response to unwinding calls on the Frame object.

Then, gdb.newest_frame() could just be redefined in terms
of selected_thread.

For this to be efficient, we'd want to fix bug #7573.

We may also want Frame.selected_frame, in which case we'd
want a fix for bug #8627.

-- 
You are receiving this mail because:
You are on the CC list for the bug.