argv[0] not the executable exactly...

[progman1]

I found that 'dune exec a/b' is executing the program such that the cwd + argv[0]
do not equal the executable's path - _build/default is nowhere to be seen.
this is a problem for my use case of the executable accessing itself for the debug info.

is this behaviour intentional?

[edit: a workaround is /proc/self/exe]

[bobot]

Does Sys.executable_name fit your need? It is generally more reliable, for example if the executable is looked into the path the shell will only give the name in argv[0].