winedbg [ options ] [ program_name [ program_arguments ] | wpid ]
winedbg --gdb [ options ] [ program_name [ program_arguments ] | wpid ]
winedbg --auto wpid
winedbg --minidump [ file.mdmp ] wpid
winedbg is a debugger for Wine. It allows:
+ debugging native Win32 applications + debugging Winelib applications + being a drop-in replacement for Dr Watson
winedbg can be used in five modes. The first argument to the program determines the mode winedbg will run in.
Without any explicit mode, this is standard winedbg operating mode. winedbg will act as the front end for the user.
winedbg will be used as a proxy for gdb. gdb will be the front end for command handling, and winedbg will proxy all debugging requests from gdb to the Win32 APIs.
This mode is used when winedbg is set up in AeDebug registry entry as the default debugger. winedbg will then display basic information about a crash. This is useful for users who don't want to debug a crash, but rather gather relevant information about the crash to be sent to developers.
This mode is similar to the --auto one, except that instead of printing the information on the screen (as --auto does), it's saved into a minidump file. The name of the file is either passed on the command line, or generated by WineDbg when none is given. This file could later on be reloaded into winedbg for further examination.
In this mode winedbg reloads the state of a debuggee which has been saved into a minidump file. See either the minidump command below, or the --minidump mode.
When in default mode, the following options are available:
- --command string
winedbg will execute the command string as if it was keyed on winedbg command line, and then will exit. This can be handy for getting the pid of running processes (winedbg --command "info proc").
- --file filename
winedbg will execute the list of commands contained in file filename as if they were keyed on winedbg command line, and then will exit.
When in gdb proxy mode, the following options are available:
Don't launch gdb directly; instead, print the target remote GDB command to execute and listen for connection from any GDB-compatible debugger. Normally, --gdb will start both the proxy debugging server and an instance of gdb for the front end. This option instructs winedbg to skip launching of gdb, and instead prints the GDB command that can be used to manually connect to the server. This command is in the form
target remote localhost:<port>
where <port> is the TCP port winedbg's proxy debugging server is bound to.
This option allows the user to replace gdb with some other debugger front end, such as ddd, kgdb, gdbgui, or Qt Creator. Regardless of whether --no-start is specified, winedbg will quit after the first connection is hung up (e.g. gdb detaches from the debuggee).
- --port port
Start the GDB proxy debugging server on the given port. If this option is not specified, winedbg will let the operating system choose any available port. This option can be used in conjunction with --no-start to specify the port the server shall be bound to.
This will run the gdb front end in a new xterm(1) window instead of using the current Unix terminal for its interface. This option is ignored if --no-start is specified.
In all modes, the rest of the command line, when passed, is used to identify which program, if any, is to be debugged:
This is the name of an executable to start for a debugging session. winedbg will actually create a process with this executable. If program_arguments are also given, they will be used as arguments for creating the process to be debugged.
winedbg will attach to the process whose Windows pid is wpid. Use the info proc command within winedbg to list running processes and their Windows pids.
If nothing is specified, you will enter the debugger without any run nor attached process. You'll have to do the job yourself.
Default mode, and while reloading a minidump file
Most of commands used in winedbg are similar to the ones from gdb. Please refer to the gdb documentations for some more details. See the gdb differences section later on to get a list of variations from gdb commands.
Aborts the debugger.
Exits the debugger.
- attach N
Attach to a Wine process (N is its Windows ID, numeric or hexadecimal). IDs can be obtained using the info process command. Note the info process command returns hexadecimal values
Detach from a Wine-process.
- thread N
Change the current thread to N (its Windows TID, numeric or hexadecimal).
Re-run the same process with the same arguments. Note: all breakpoints of precedent process are no longer available.
- run arg1 arg2...
Re-run the same process with arguments arg1 arg2.... Note: all breakpoints of precedent process are no longer available.
Prints some help on the commands.
- help info
Prints some help on info commands
Flow control commands
Continue execution until next breakpoint or exception.
Pass the exception event up to the filter chain.
Continue execution until next C line of code (enters function call)
Continue execution until next C line of code (doesn't enter function call)
Execute next assembly instruction (enters function call)
Execute next assembly instruction (doesn't enter function call)
Execute until return of current function is reached.
cont, step, next, stepi, nexti can be postfixed by a number (N), meaning that the command must be executed N times before control is returned to the user.
- enable N
Enables (break|watch)-point N
- disable N
Disables (break|watch)-point N
- delete N
Deletes (break|watch)-point N
- cond N
Removes any existing condition to (break|watch)-point N
- cond N expr
Adds condition expr to (break|watch)-point N. expr will be evaluated each time the (break|watch)-point is hit. If the result is a zero value, the breakpoint isn't triggered.
- break * N
Adds a breakpoint at address N
- break id
Adds a breakpoint at the address of symbol id
- break id N
Adds a breakpoint at the line N inside symbol id.
- break N
Adds a breakpoint at line N of current source file.
Adds a breakpoint at current $PC address.
- watch * N
Adds a watch command (on write) at address N (on 4 bytes).
- watch id
Adds a watch command (on write) at the address of symbol id. Size depends on size of id.
- rwatch * N
Adds a watch command (on read) at address N (on 4 bytes).
- rwatch id
Adds a watch command (on read) at the address of symbol id. Size depends on size of id.
- info break
Lists all (break|watch)-points (with their state).
You can use the symbol EntryPoint to stand for the entry point of the Dll.
When setting a (break|watch)-point by id, if the symbol cannot be found (for example, the symbol is contained in a not yet loaded module), winedbg will recall the name of the symbol and will try to set the breakpoint each time a new module is loaded (until it succeeds).
Print calling stack of current thread.
- bt N
Print calling stack of thread of ID N. Note: this doesn't change the position of the current frame as manipulated by the up & dn commands).
Goes up one frame in current thread's stack
- up N
Goes up N frames in current thread's stack
Goes down one frame in current thread's stack
- dn N
Goes down N frames in current thread's stack
- frame N
Sets N as the current frame for current thread's stack.
- info locals
Prints information on local variables for current function frame.
Directory & source file manipulation
- show dir
Prints the list of dirs where source files are looked for.
- dir pathname
Adds pathname to the list of dirs where to look for source files
Deletes the list of dirs where to look for source files
- symbolfile pathname
Loads external symbol definition file pathname
- symbolfile pathname N
Loads external symbol definition file pathname (applying an offset of N to addresses)
Lists 10 source lines forwards from current position.
- list -
Lists 10 source lines backwards from current position
- list N
Lists 10 source lines from line N in current file
- list pathname:N
Lists 10 source lines from line N in file pathname
- list id
Lists 10 source lines of function id
- list * N
Lists 10 source lines from address N
You can specify the end target (to change the 10 lines value) using the ',' separator. For example:
- list 123, 234
lists source lines from line 123 up to line 234 in current file
- list foo.c:1,56
lists source lines from line 1 up to 56 in file foo.c
A display is an expression that's evaluated and printed after the execution of any winedbg command.
- info display
Lists the active displays
- display expr
Adds a display for expression expr
- display /fmt expr
Adds a display for expression expr. Printing evaluated expr is done using the given format (see print command for more on formats)
- del display N
- undisplay N
Deletes display N
Disassemble from current position
- disas expr
Disassemble from address expr
- disas expr,expr
Disassembles code between addresses specified by the two expressions
Memory (reading, writing, typing)
- x expr
Examines memory at address expr
- x /fmt expr
Examines memory at address expr using format fmt
- print expr
Prints the value of expr (possibly using its type)
- print /fmt expr
Prints the value of expr (possibly using its type)
- set var = expr
Writes the value of expr in var variable
- whatis expr
Prints the C type of expression expr
is either letter or count letter, where letter can be:
an ASCII string
a UTF16 Unicode string
32-bit unsigned hexadecimal integer
32-bit signed decimal integer
16-bit unsigned hexadecimal integer
character (only printable 0x20-0x7f are actually printed)
8-bit unsigned hexadecimal integer
Expressions in Wine Debugger are mostly written in a C form. However, there are a few discrepancies:
Identifiers can take a '!' in their names. This allows mainly to specify a module where to look the ID from, e.g. USER32!CreateWindowExA.
In a cast operation, when specifying a structure or a union, you must use the struct or union keyword (even if your program uses a typedef).
When specifying an identifier, if several symbols with this name exist, the debugger will prompt for the symbol you want to use. Pick up the one you want from its number.
minidump file.mdmp saves the debugging context of the debuggee into a minidump file called file.mdmp.
Information on Wine internals
- info class
Lists all Windows classes registered in Wine
- info class id
Prints information on Windows class id
- info share
Lists all the dynamic libraries loaded in the debugged program (including .so files, NE and PE DLLs)
- info share N
Prints information on module at address N
- info regs
Prints the value of the CPU registers
- info all-regs
Prints the value of the CPU and Floating Point registers
- info segment
Lists all allocated segments (i386 only)
- info segment N
Prints information on segment N (i386 only)
- info stack
Prints the values on top of the stack
- info map
Lists all virtual mappings used by the debugged program
- info map N
Lists all virtual mappings used by the program of Windows pid N
- info wnd
Displays the window hierarchy starting from the desktop window
- info wnd N
Prints information of Window of handle N
- info process
Lists all w-processes in Wine session
- info thread
Lists all w-threads in Wine session
- info frame
Lists the exception frames (starting from current stack frame). You can also pass, as optional argument, a thread id (instead of current thread) to examine its exception frames.
Debug messages can be turned on and off as you are debugging using the set command, but only for channels initialized with the WINEDEBUG environment variable.
- set warn + win
Turns on warn on win channel
- set + win
Turns on warn/fixme/err/trace on win channel
- set - win
Turns off warn/fixme/err/trace on win channel
- set fixme - all
Turns off fixme class on all channels
See the gdb documentation for all the gdb commands.
However, a few Wine extensions are available, through the monitor command:
- monitor wnd
Lists all windows in the Wine session
- monitor proc
Lists all processes in the Wine session
- monitor mem
Displays memory mapping of debugged process
Auto and minidump modes
Since no user input is possible, no commands are available.
When used in gdb proxy mode, WINE_GDB specifies the name (and the path) of the executable to be used for gdb. "gdb" is used by default.
The first version was written by Eric Youngdale.
See Wine developers list for the rest of contributors.
Bugs can be reported on the Wine bug tracker.
winedbg is part of the Wine distribution, which is available through WineHQ, the Wine development headquarters.
Wine documentation and support.