debugger startup
eric pouech
eric.pouech at wanadoo.fr
Fri Apr 13 10:58:43 CDT 2001
ok. I finally found out what's wrong
let's say process A launches thru CreateProcess a shell script
/home/me/foo
this shell script, in turn does an exec winedbg $* to launch the
debugger
what happens is that, in the server, the created process name is set to
/home/me/foo, whereas, when the debugger starts, argv[0] is set to
winedbg
what the process creation (open_winelib_app) gets from the server is the
/home/me/foo filename, which is wrong because of the exec
as I understand the code, it's better to use the name from the server
because it may be a windows style one (whereas argv[0] is always a unix
one)
apart, from always using argv[0] (and transposing it to a windows
filename
when needed), is there another fix ?
A+
--
---------------
Eric Pouech (http://perso.wanadoo.fr/eric.pouech/)
"The future will be better tomorrow", Vice President Dan Quayle
More information about the wine-devel
mailing list