http://bugs.winehq.org/show_bug.cgi?id=27052
Frédéric Delanoy frederic.delanoy@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download, source Status|UNCONFIRMED |NEW CC| |frederic.delanoy@gmail.com Ever Confirmed|0 |1
--- Comment #1 from Frédéric Delanoy frederic.delanoy@gmail.com 2011-09-07 03:09:37 CDT --- (In reply to comment #0)
I couldn't figure out why winedbg complained "Can't attach process 42db: error 87" when I typed "attach 17115". I know the PID of my Windows executable, as provided by top, ps, System Activity, etc.
You need to supply the *Wine/Windows PID* of the process, e.g. using the "info process" command to winedbg, and this *isn't* the UNIX pid. This is mentioned further down in winedbg(1), but it would be so much clearer if the man page, the "info process" command and other documentation consistently used "wpid", as http://www.winehq.org/docs/winedev-guide/debugger does.
There is missing help that also needs to use "wpid":
- winedbg --help's usage output doesn't mention the --auto wpid usage (though I
couldn't get this to work).
- the help command within winedbg doesn't mention "attach wpid"
Confirmed. Although to be fair, manpage tells "winedbg will attach to the process which pid is pid (pids refer to Win32 pids, not Unix pids)"