Commit 903562e1 authored by Frédéric Delanoy's avatar Frédéric Delanoy Committed by Alexandre Julliard

winedbg: Use consistently wpid in documentation.

parent 7a12ebca
...@@ -49,6 +49,7 @@ void print_help(void) ...@@ -49,6 +49,7 @@ void print_help(void)
"subset of the commands that gdb accepts.", "subset of the commands that gdb accepts.",
"The commands currently are:", "The commands currently are:",
" help quit", " help quit",
" attach <wpid> detach",
" break [*<addr>] watch | rwatch *<addr>", " break [*<addr>] watch | rwatch *<addr>",
" delete break bpnum disable bpnum", " delete break bpnum disable bpnum",
" enable bpnum condition <bpnum> [<expr>]", " enable bpnum condition <bpnum> [<expr>]",
......
...@@ -568,11 +568,11 @@ static int dbg_winedbg_usage(BOOL advanced) ...@@ -568,11 +568,11 @@ static int dbg_winedbg_usage(BOOL advanced)
dbg_printf("Usage:\n" dbg_printf("Usage:\n"
" winedbg cmdline launch process 'cmdline' (as if you were starting\n" " winedbg cmdline launch process 'cmdline' (as if you were starting\n"
" it with wine) and run WineDbg on it\n" " it with wine) and run WineDbg on it\n"
" winedbg <num> attach to running process of pid <num> and run\n" " winedbg <num> attach to running process of wpid <num> and run\n"
" WineDbg on it\n" " WineDbg on it\n"
" winedbg --gdb cmdline launch process 'cmdline' (as if you were starting\n" " winedbg --gdb cmdline launch process 'cmdline' (as if you were starting\n"
" wine) and run gdb (proxied) on it\n" " wine) and run gdb (proxied) on it\n"
" winedbg --gdb <num> attach to running process of pid <num> and run\n" " winedbg --gdb <num> attach to running process of wpid <num> and run\n"
" gdb (proxied) on it\n" " gdb (proxied) on it\n"
" winedbg file.mdmp reload the minidump file.mdmp into memory and run\n" " winedbg file.mdmp reload the minidump file.mdmp into memory and run\n"
" WineDbg on it\n" " WineDbg on it\n"
......
...@@ -3,15 +3,15 @@ ...@@ -3,15 +3,15 @@
winedbg \- Wine debugger winedbg \- Wine debugger
.SH SYNOPSIS .SH SYNOPSIS
.B winedbg .B winedbg
.RI "[ " options " ] [ " program_name " [ " program_arguments " ] | " pid " ]" .RI "[ " options " ] [ " program_name " [ " program_arguments " ] | " wpid " ]"
.PP .PP
.B winedbg --gdb .B winedbg --gdb
.RI "[ " options " ] [ " program_name " [ " program_arguments " ] | " pid " ]" .RI "[ " options " ] [ " program_name " [ " program_arguments " ] | " wpid " ]"
.PP .PP
.BI "winedbg --auto " pid .BI "winedbg --auto " wpid
.PP .PP
.B winedbg --minidump .B winedbg --minidump
.RI "[ " file.mdmp " ] " pid .RI "[ " file.mdmp " ] " wpid
.PP .PP
.BI "winedbg " file.mdmp .BI "winedbg " file.mdmp
.SH DESCRIPTION .SH DESCRIPTION
...@@ -84,10 +84,10 @@ This is the name of an executable to start for a debugging ...@@ -84,10 +84,10 @@ This is the name of an executable to start for a debugging
session. \fBwinedbg\fR will actually create a process with this session. \fBwinedbg\fR will actually create a process with this
executable. If \fIprograms_arguments\fR are also given, they will be executable. If \fIprograms_arguments\fR are also given, they will be
used as arguments for creating the process to be debugged. used as arguments for creating the process to be debugged.
.IP \fIpid\fR .IP \fIwpid\fR
\fBwinedbg\fR will attach to the process which pid is \fIpid\fR (pids \fBwinedbg\fR will attach to the process which Windows pid is \fIwpid\fR.
refer to Win32 pids, not Unix pids). Use the \fBinfo proc\fR command Use the \fBinfo proc\fR command within \fBwinedbg\fR to list running processes
within \fBwinedbg\fR to list running processes and their Win32 pids. and their Windows pids.
.IP \fBdefault\fR .IP \fBdefault\fR
If nothing is specified, you will enter the debugger without any run If nothing is specified, you will enter the debugger without any run
nor attached process. You'll have to do the job yourself. nor attached process. You'll have to do the job yourself.
...@@ -106,7 +106,7 @@ Aborts the debugger. ...@@ -106,7 +106,7 @@ Aborts the debugger.
.IP \fBquit\fR .IP \fBquit\fR
Exits the debugger. Exits the debugger.
.IP \fBattach\ \fIN\fR .IP \fBattach\ \fIN\fR
Attach to a Wine process (\fIN\fR is its ID, numeric or hexadecimal). Attach to a Wine process (\fIN\fR is its Windows ID, numeric or hexadecimal).
IDs can be obtained using the \fBinfo\ process\fR command. Note the IDs can be obtained using the \fBinfo\ process\fR command. Note the
\fBinfo\ process\fR command returns hexadecimal values \fBinfo\ process\fR command returns hexadecimal values
.IP .IP
...@@ -346,7 +346,7 @@ Prints the values on top of the stack ...@@ -346,7 +346,7 @@ Prints the values on top of the stack
.IP \fBinfo\ map\fR .IP \fBinfo\ map\fR
Lists all virtual mappings used by the debugged program Lists all virtual mappings used by the debugged program
.IP \fBinfo\ map\ \fIN\fR .IP \fBinfo\ map\ \fIN\fR
Lists all virtual mappings used by the program of pid \fIN\fR Lists all virtual mappings used by the program of Windows pid \fIN\fR
.IP \fBinfo\ wnd\fR .IP \fBinfo\ wnd\fR
Displays the window hierarchy starting from the desktop window Displays the window hierarchy starting from the desktop window
.IP \fBinfo\ wnd\ \fIN\fR .IP \fBinfo\ wnd\ \fIN\fR
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment