Box64 Trace Stops After my_execv Execution

[parkjunhyung2021046762]

Hi,

When running Wine with box64 using the BOX64_TRACE=1 option, after executing my_execv, no further box64 trace output appears. Is this the expected behavior? Could you explain in detail what happens after my_execv is executed?
(For reference, I executed a simple 64‑bit hello.exe file that just prints 'hello!'.)

Below is the last part of the trace.

[�[31mBOX64�[0m] ES=0x002b CS=0x0033 SS=0x002b DS=0x002b FS=0x0000 GS=0x0000 FSBASE=0x5d9d73c0 GSBASE=(nil)
RAX=0000000000000032 RCX=00007fff00073485 RDX=000000005d997070 RBX=000000005d997040 RSP=00007466f2ffec08 FLAGS=-------
RBP=000000005d997048 RSI=000000005d997040 RDI=000000005d9970b0 R8=000000005d986960 R9=0000000000400000
R10=0000000000040661 R11=00000000756e6547 R12=00007fff000734a9 R13=00007466f2ffede0 R14=000000000000006c
R15=0000000000000002 RIP=00007466f3692420 0x7466f3692420: Native call to 0x34bbaa70 => my_execv(wine)

[ptitSeb]

When execv is used, another process is launched, and the both process might share the same output, or the new process is a native one and will not trace (and the parent just end).
You can use also BOX64_TRACE_FILE=/tmp/log-box64-%pid.txt to have each process writting in it's own file istead, it might be better.

Also, running a TRACE dump on wine will end up with a huge huge dump! Don"t forget to use BOX64_DYNAREC_TRACE=1 also to trace the Dynarec part, else you will only have the trace of the interpreter, wich might not be a lot.