Skip to content
Projects
Groups
Snippets
Help
This project
Loading...
Sign in / Register
Toggle navigation
W
wine-cw
Project
Project
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Registry
Registry
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
wine
wine-cw
Commits
f815c264
Commit
f815c264
authored
Jun 21, 2022
by
Jinoh Kang
Committed by
Alexandre Julliard
Jun 24, 2022
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
winedbg: Clarify options specific to GDB proxy mode.
Signed-off-by:
Jinoh Kang
<
jinoh.kang.kr@gmail.com
>
parent
313f75a0
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
30 additions
and
9 deletions
+30
-9
winedbg.man.in
programs/winedbg/winedbg.man.in
+30
-9
No files found.
programs/winedbg/winedbg.man.in
View file @
f815c264
...
@@ -69,17 +69,38 @@ will exit.
...
@@ -69,17 +69,38 @@ will exit.
When in \fBgdb\fR proxy mode, the following options are available:
When in \fBgdb\fR proxy mode, the following options are available:
.PP
.PP
.IP \fB--no-start\fR
.IP \fB--no-start\fR
\fBgdb\fR will not be automatically
Don't launch \fBgdb\fR directly; instead, print the \fBtarget remote\fR
started. Relevant information for starting \fBgdb\fR is printed on
GDB command to execute and listen for connection from any GDB-compatible
screen. This is somehow useful when not directly using \fBgdb\fR but
debugger. Normally, \fB--gdb\fR will start both the proxy debugging server
some graphical front-ends, like \fBddd\fR or \fBkgbd\fR.
and an instance of \fBgdb\fR for the front end. This option instructs
\fBwinedbg\fR to skip launching of \fBgdb\fR, and instead prints
the GDB command that can be used to manually connect to the server.
This command is in the form
.IP
.in +4n
.EX
target remote localhost:\fI<port>\fR
.EE
.in
.IP
where \fI<port>\fR is the TCP port \fBwinedbg\fR's proxy debugging server is bound to.
.IP
This option allows the user to replace \fBgdb\fR with some other
debugger front end, such as \fBddd\fR, \fBkgdb\fR, \fBgdbgui\fR, or Qt Creator.
Regardless of whether \fB--no-start\fR is specified, \fBwinedbg\fR will quit
after the first connection is hung up (e.g. \fBgdb\fR detaches from the
debuggee).
.IP \fB--port\fR\ \fIport\fR
.IP \fB--port\fR\ \fIport\fR
Start the \fBgdb\fR server on the given port. If this option is not
Start the GDB proxy debugging server on the given port. If this option is not
specified, a randomly chosen port will be used. If \fB--no-start\fR is
specified, \fBwinedbg\fR will let the operating system choose any available port.
specified, the port used will be printed on startup.
This option can be used in conjunction with \fB--no-start\fR to specify the port the
server shall be bound to.
.IP \fB--with-xterm\fR
.IP \fB--with-xterm\fR
This will run \fBgdb\fR in its own xterm instead of using the current
This will run the \fBgdb\fR front end in a new
Unix console for textual display.
.BR xterm (1)
window instead of using the current Unix terminal for its interface.
This option is ignored if \fB--no-start\fR is
specified.
.PP
.PP
In all modes, the rest of the command line, when passed, is used to
In all modes, the rest of the command line, when passed, is used to
identify which program, if any, is to be debugged:
identify which program, if any, is to be debugged:
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment