Is there a way to know about current "until"/"advance" execution?

Simon Sobisch simonsobisch@gnu.org
Fri Nov 5 09:14:36 GMT 2021


For a silent breakpoint the following commands are very useful

break something
command
   silent
   do_something
   continue
end

or the similar version in a python script using the silent attribute and 
continue as a command.

I've recently seen a problem with this the first time - it break any 
active "until"


break 120
command
   silent
   continue
end
break 140
until 123


will execute until 140 (with a function that just executes each line), 
while the user "intended" to go until line 123.

Similar applies to "advance".


The workaround as a user:
instead of using "until": create a temporary maintenance breakpoint in 
line 123 and "continue".
... but as the break 120 in the sample above is scripted and not 
executed by a user this cannot be applied.

Questions:
* Is there a more direct way to "preserve" the running "until"/"advance" 
in GDB scripting or with Python?

* Is there a way in Python to know about the current active "until" (so 
this can be re-done instead of "continue"/"until" in the above example)?

* If there isn't an option for this, can you please consider this as a 
Feature Request for the Python API of GDB?

Thanks,
Simon


More information about the Gdb mailing list