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
define rr release <cmd> [args...] command that does something equivalent to the following
if [[ "$RUNNING_UNDER_RR"== 1 ]];then
rr record --nested=release env --unset=RUNNING_UNDER_RR "$@"else"$@"fi
make a release-on-exec configuration that can be passed to rr record that releases a process on fork+exec. (ideally without affecting other things such as create new thread, fork without exec i.e. process spawn worker process, etc.)
The second would be more convenient, but the first would be more flexible, assume the user can modify and recompile the process.
The text was updated successfully, but these errors were encountered:
Maybe rr record --nested=release should just not record at all, and always exec the child directly when not already running under rr? It seems a bit weird to have it not create a recording when run under rr, but have it create a recording when not run under rr. @Keno what do you think?
Motivation: sometimes it is desirable to make
rr
not track a subprocess spawned by fork+exec.(see linux - Support in rr-debugger for not recording a subprocess? - Stack Overflow )
I think there could be two ways
define
rr release <cmd> [args...]
command that does something equivalent to the followingmake a
release-on-exec
configuration that can be passed torr record
that releases a process on fork+exec. (ideally without affecting other things such as create new thread, fork without exec i.e. process spawn worker process, etc.)The second would be more convenient, but the first would be more flexible, assume the user can modify and recompile the process.
The text was updated successfully, but these errors were encountered: