I noticed that --auto_run adds the target to the list but doesn't actually start it.
Had a quick look at the code — I guess it might be related to these two spots:
|
//- rjf: auto run |
|
if(auto_run) |
|
{ |
|
auto_run = 0; |
|
rd_cmd(RD_CmdKind_LaunchAndRun); |
|
} |
|
// rjf: run -> no active targets, no processes, but we only have one target? -> just launch it, then select it |
|
if((kind == RD_CmdKind_Run || |
|
kind == RD_CmdKind_StepInto || |
|
kind == RD_CmdKind_StepOver) && processes.count == 0 && targets.count == 1 && !has_active_targets) |
|
{ |
|
rd_cmd(kind == RD_CmdKind_Run ? RD_CmdKind_LaunchAndRun : RD_CmdKind_LaunchAndStepInto, .cfg = targets.first->v->id); |
|
rd_cmd(RD_CmdKind_SelectTarget, .cfg = targets.first->v->id); |
|
break; |
|
} |
I noticed that
--auto_runadds the target to the list but doesn't actually start it.Had a quick look at the code — I guess it might be related to these two spots:
raddebugger/src/raddbg/raddbg_main.c
Lines 972 to 977 in 7048a87
raddebugger/src/raddbg/raddbg_core.c
Lines 12294 to 12302 in 7048a87