"dashboard" in a hookpost-next with recent gdb versions fails about gdb-dashboard HOT 8 CLOSED

I'm maybe misunderstanding your problem but, why are you hooking dashboard to next? The default behavior is to draw the dashboard whenever the target stops, hence after each next.

from gdb-dashboard.

Ah I hadn't realized that, but the fact is, I do a bunch of other stuff in my hookpost-next, namely I tell my current vim instance to go to the file / line stopped on (which, just like "dashboard", grabs the gdb.selected_frame(). So I still need to be able to do stuff in hookpost-next and the original problem still stands. I was just trying to give you a simple repro case without dragging my other vim scripts into the mix.

Can you give me a pointer to how you're running dashboard when the target stops? Since that is working fine whereas the hookpost-next is not, I'll try just using that method for my vim stuff.

from gdb-dashboard.

Just to be clear: Any call to gdb.selected_frame() seems to fail in a hookpost-next... it's not just a 'dashboard' thing. It's very very likely this is a gdb issue and not really a gdb-dashboard issue, but at this point I'm curious what you're using to run 'dashboard' on stoppage so I can just copy that :)

from gdb-dashboard.

(No need to respond on that, I see how it's done)

from gdb-dashboard.

OK, so I can confirm that with the latest GDB version (from bminor/binutils-gdb) the following fails as you say with gdb.error: No frame is currently selected.:

define hookpost-next
python print gdb.selected_frame()
end

Whereas it work with GDB version 7.7; they must have broken something I guess...

Anyway the dashboard is not affected because I'm registering to that event using the Python API as you can see here. Hope this helps.

from gdb-dashboard.

So as it doesn't seem to be related to the dashboard, can I close this? Feel free to comment here or reach me by email if you have any questions.

from gdb-dashboard.

Thanks for taking the time to confirm that, it's good to have a sanity check.

After using the python API to connect to the stop event, all is well again. Thanks!

from gdb-dashboard.

Great! You're welcome.

from gdb-dashboard.