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
While standard software breakpoints (break) work for PAL and application, it seems currently for libos one needs hardware breakpoints (hbreak) to interrupt the program (setting breakpoints for libos functions with break seems to work but the program never stops ...). I think this previously did work with break also for libos but i'm not 100% sure and, more importantly, i don't know when it stopped working. Using hbreak instead of break is not a big deal, but thought i would create this issue so folks could find this workaround while searching issues if they run in the same problem ...
PS: Note that CI does test gdb break points but only for PAL (which works), not libos (which doesn't) ....
Steps to reproduce
start a program using protected files with GDB=1 gramine-direct ...
set a breakpoint with b ipf_open
run program with run
Expected results
gdb should stop when ipf_open is encountered
Actual results
gdb runs to the end (even though, with log_level=trace one can see that ipf_open was called
BTW: Unless somebody knows right away what the issue is, this is probably not worth spending time investigating. Makes me wonder, though, should i maybe create a small PR to update the documentation with a corresponding comment?
I'm pretty sure it worked correctly in the past, it's quite unlucky that this scenario wasn't tested.
Instead of documenting this, I'd rather find someone to debug and fix it, as it's clearly a bug :)
Description of the problem
While standard software breakpoints (
break
) work for PAL and application, it seems currently for libos one needs hardware breakpoints (hbreak
) to interrupt the program (setting breakpoints for libos functions withbreak
seems to work but the program never stops ...). I think this previously did work withbreak
also for libos but i'm not 100% sure and, more importantly, i don't know when it stopped working. Usinghbreak
instead ofbreak
is not a big deal, but thought i would create this issue so folks could find this workaround while searching issues if they run in the same problem ...PS: Note that CI does test gdb break points but only for PAL (which works), not libos (which doesn't) ....
Steps to reproduce
GDB=1 gramine-direct ...
b ipf_open
run
Expected results
gdb should stop when
ipf_open
is encounteredActual results
gdb runs to the end (even though, with
log_level=trace
one can see thatipf_open
was calledGramine commit hash
68b9602
The text was updated successfully, but these errors were encountered: