[Bug 27052] New: winedbg and its man page should use "wpid" consistently for Windows' process ID
http://bugs.winehq.org/show_bug.cgi?id=27052
Summary: winedbg and its man page should use "wpid" consistently for Windows' process ID Product: Wine Version: 1.3.15 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winedbg AssignedTo: wine-bugs@winehq.org ReportedBy: info@skierpage.com
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"
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)"
http://bugs.winehq.org/show_bug.cgi?id=27052
Frédéric Delanoy frederic.delanoy@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Fixed by SHA1| |903562e104a744a75d3b49f6a98 | |3b831b5a461aa Status|NEW |RESOLVED Resolution| |FIXED
--- Comment #2 from Frédéric Delanoy frederic.delanoy@gmail.com 2013-09-02 14:59:41 CDT --- Fixed by 903562e104a744a75d3b49f6a983b831b5a461aa.
http://bugs.winehq.org/show_bug.cgi?id=27052
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #3 from Alexandre Julliard julliard@winehq.org 2013-09-13 13:19:51 CDT --- Closing bugs fixed in 1.7.2.
http://bugs.winehq.org/show_bug.cgi?id=27052
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |1.6.x
http://bugs.winehq.org/show_bug.cgi?id=27052
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|1.6.x |---
--- Comment #4 from Alexandre Julliard julliard@winehq.org 2013-11-15 13:40:32 CST --- Removing 1.6.x milestone from bugs included in 1.6.1.
-
wine-bugs＠winehq.org