[Bug python/16281] python frame comparison should take inferior into account (including restarted inferior)

["xdje42 at gmail dot com" <sourceware-bugzilla at sourceware dot org>]

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

--- Comment #3 from Doug Evans <xdje42 at gmail dot com> ---
(In reply to Pedro Alves from comment #2)
> > python's frame comparison support just calls frame_id_eq, but that can return > true for the "same" frame in different inferiors.
> 
> Or different threads of the same inferior, even.

I know.

> Usually that won't happen
> because each thread will have its own stack frame, but it can happen.  E.g.,
> if previous thread exits, and new thread reuses stack.  Or, if
> signal/exception handler runs on its own stack, no matter which thread was
> current, the same frame can be seen from both threads.

Cases I entertained myself.

> In a way, returning true for f1 == f2 isn't that much of a stretch.  They
> are two different instantiations of the same frame.  You'd want that to be
> true if e.g., you were debugging a multi-process program (multiple forks),
> and wanted to do something similar to gdb's builtin local watchpoint
> handling (stop only on frame XX).  I think it should be up to the higher
> level code to make sure it makes sense to compare the frames.

I'm not prepared to go that far, but whatever.

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