[Bug python/18567] Frame filters apply to 'backtrace' but not 'frame' command

["palves at redhat dot com" <sourceware-bugzilla at sourceware dot org>]

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

--- Comment #7 from Pedro Alves <palves at redhat dot com> ---
> I would probably be confused if I was in frame #0 and typed "up"
> and ended up in frame #3.

Maybe I'm thinking of the opposite scenario.

Say, if you're debugging for example GDB's Python code, and a filter hides the
Python interpreter detail of gdb code calling Python code calling gdb code,
like:

#0  ... gdb/python/python.c:99
#1  ... something.py:99
  #2  ... python-interp-internals.c
  ...
  #10 ... python-interp-internals.c
#11 ... gdb/python/python.c:99

I'd think that "up" on frame #1 going straight to frame #11 would be helpful.

Likewise in the "hiding glib signal-emission frames" use case.

> Also, one must consider that if frame filters apply to up and down,
> then why not step, next, and finish?  And then you're in for some
> difficult implementation stuff I think...

At least the inline-frames example shows that this should be possible.
GDB already treats "step" when stopped at an inline frame, differently
(infcmd.c:prepare_one_step -> inline_skipped_frames), which I was imagining
could be generalized to all kinds of virtual frames.

But yeah, if a simpler approach is already helpful, by all means!

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