WineHQ Bugzilla – Bug 27052 – winedbg and its man page should use "wpid" consistently for Windows' process ID

Bugzilla

Last modified: 2013-11-15 13:40:32 UTC

winedbg and its man page should use "wpid" consistently for Windows' process ID

Bug 27052 - winedbg and its man page should use "wpid" consistently for Windows' process ID


Summary:	winedbg and its man page should use "wpid" consistently for Windows' process ID

Status:	CLOSED FIXED

AppDB:	Show Apps affected by this bug
Product:	Wine
Classification:	Unclassified
Component:	winedbg
Version:	1.3.15
Hardware:	x86-64 Linux

Importance:	P2 normal
Target Milestone:	---
Assigned To:	Mr. Bugs

URL:
Keywords:	download, source

Depends on:
Blocks:
	Show dependency tree

Reported:	2011-05-04 18:44 UTC by skierpage
Modified:	2013-11-15 13:40 UTC (History)
CC List:	1 user (show)

See Also:
Regression SHA1:
Fixed by SHA1:	903562e104a744a75d3b49f6a983b831b5a461aa
Distribution:	---
Staged patchset:

Attachments
Add an attachment (back traces, logs, proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description skierpage 2011-05-04 18:44:18 UTC

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"

Comment 1 Frédéric Delanoy 2011-09-07 03:09:37 UTC

(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)"

Comment 2 Frédéric Delanoy 2013-09-02 14:59:41 UTC

Fixed by 903562e104a744a75d3b49f6a983b831b5a461aa.

Comment 3 Alexandre Julliard 2013-09-13 13:19:51 UTC

Closing bugs fixed in 1.7.2.

Comment 4 Alexandre Julliard 2013-11-15 13:40:32 UTC

Removing 1.6.x milestone from bugs included in 1.6.1.