This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: RFC: lazily call save_current_space_and_thread
Pedro> I'm guessing you're trying all-stop. In non-stop, I _think_
Pedro> you'll much more rarely see a NULL selected frame here.
Nope, I do this before my test:
set target-async on
set schedule-multiple on
set pagination off
set detach-on-fork off
set non-stop on
I can't say that I understand everything that happens in this mode.
"run" appears to work in the background, which is mysterious to me.
And, if I C-c gdb, I just get "Quit." back, and then gdb is in a weird
state (I can't "continue" any inferior and if I try "run" I get an
internal error).
I am planning to debug these next; but if you know what is going on
already...
Tom