You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We introduced step into XXX for #655 but I realized that step into is a bit strange for me because step command should stop at the next operation (line, call, ...) immediately.
Also into XXX does not make sense if the XXX is called after returning from the current frame.
deffoo# break hereendfoobar
If we stop at the line 2 (break here line) and dispatch step into bar, then
return from foo
call bar
break at the first line of bar
I think continue until XXX, continue to XXX or just continue XXX is another alternative but not sure it makes sense a lot.
Maybe break YYY does not make sense too.
step until XXX is another candidate. It is similar to step 10 (repeat step 10 times).
until: Continue the program until it reaches to the next line even if at the end of loop. next command stops the program at the beginning of the loop, but until command stops just after loop.
until <loc>: Continue the program until it reaches to the <loc>or it returns from the current frame (~= finish).
gdb skips the recursive function calls but I think it is okay to respect the any recursive call (and advance command is too much).
In other words, this until command is almost advance command.
gdb's until doesn't make pending temporary breakpoint for the unknown location (break makes pending breakpoints).
we can skip unknown location. But not clear we can detect unknown method. maybe we can show error if the symbol in Symbal.all_symbols doesn't include the given location.
Do you think the jump command is equally an option?
jump <loc>
The problem is the fact it doesn't seem to exist jump without a location even though I can infer it could resume until the next breakpoint or at the end of the frame. 🤔
Activity
ko1 commentedon Nov 8, 2022
untilcommand on gdb is similar https://sourceware.org/gdb/download/onlinedocs/gdb/Continuing-and-Stepping.html so we should implementuntilcommand.So
step into XXXshould beuntil XXXoru XXX.[-]`step into XXX` to `continue until XXX`?[/-][+]`step into XXX` to `until XXX`[/+]ko1 commentedon Nov 8, 2022
until: Continue the program until it reaches to the next line even if at the end of loop.nextcommand stops the program at the beginning of the loop, butuntilcommand stops just after loop.until <loc>: Continue the program until it reaches to the<loc>or it returns from the current frame (~=finish).ko1 commentedon Nov 8, 2022
gdb skips the recursive function calls but I think it is okay to respect the any recursive call (and
advancecommand is too much).In other words, this
untilcommand is almostadvancecommand.ko1 commentedon Nov 8, 2022
gdb's
untildoesn't make pending temporary breakpoint for the unknown location (breakmakes pending breakpoints).we can skip unknown location. But not clear we can detect unknown method. maybe we can show error if the symbol in
Symbal.all_symbolsdoesn't include the given location.wenderjean commentedon Nov 9, 2022
Do you think the
jumpcommand is equally an option?jump <loc>The problem is the fact it doesn't seem to exist
jumpwithout a location even though I can infer it could resume until the next breakpoint or at the end of the frame. 🤔ko1 commentedon Nov 11, 2022
https://sourceware.org/gdb/current/onlinedocs/gdb/Jumping.html
Known
jumpcommand doesn't do the proposed behavior.`until` command
`until` command
bquorning commentedon Apr 4, 2024
Byebug actually uses the
continue XXXsyntax, and when using the debug gem I always hitc 42instead ofu 42because of muscle memory.