How to log windbgx.exe output to a file?
In this documentation (https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/windbg-command-line-preview) it says that the following command should log the output to a file:
WinDbgX.exe logo ".myfile.txt"
However the windbg tells me that the debugger cannot find the file specified. I did run the command from powershell where myfile.txt is located so im not sure what the correct syntax is. I also tried other variants such as:
WinDbgX.exe "logo .aaa.txt"
I also tried passing the parameter after specifying a particular imagine file to debug:
windbgx.exe myapp.exe logo myfile.txt
powershell cmd windbg
asked Nov 25 '18 at 1:57
mblmbl
6818
|
show 4 more comments
In this documentation (https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/windbg-command-line-preview) it says that the following command should log the output to a file:
WinDbgX.exe logo ".myfile.txt"
However the windbg tells me that the debugger cannot find the file specified. I did run the command from powershell where myfile.txt is located so im not sure what the correct syntax is. I also tried other variants such as:
WinDbgX.exe "logo .aaa.txt"
I also tried passing the parameter after specifying a particular imagine file to debug:
windbgx.exe myapp.exe logo myfile.txt
powershell cmd windbg
asked Nov 25 '18 at 1:57
mblmbl
6818
Is that something powershell specific? Can you run it in cmd?
– Mike Twc
Nov 25 '18 at 2:32
It's not. I also tried from cmd.
– mbl
Nov 25 '18 at 2:37
Did you tried full path of the file? I think "." will be a working directory of windbg, not powershell's
– Mike Twc
Nov 25 '18 at 2:42
From PS I tried: WinDbgX.exe .myapp.exe logo "C:UsersmynameDesktopaaa.txt" and I don't get an error anymore. However nothing is logged to my text file after I break into my program and use some debugger commands just to test. The first line of the command window that appears when the debugger launch is this: CommandLine: .myapp.exe logo C:UsersmynameDesktopaaa.txt
– mbl
Nov 25 '18 at 2:50
1
Possible typo in the documentation. Try-logowith a leading hyphen. Without the hyphen, it looks like you're trying to debug a program calledlogo.
– Raymond Chen
Nov 25 '18 at 4:13
|
show 4 more comments
In this documentation (https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/windbg-command-line-preview) it says that the following command should log the output to a file:
WinDbgX.exe logo ".myfile.txt"
However the windbg tells me that the debugger cannot find the file specified. I did run the command from powershell where myfile.txt is located so im not sure what the correct syntax is. I also tried other variants such as:
WinDbgX.exe "logo .aaa.txt"
I also tried passing the parameter after specifying a particular imagine file to debug:
windbgx.exe myapp.exe logo myfile.txt
powershell cmd windbg
asked Nov 25 '18 at 1:57
mblmbl
6818
In this documentation (https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/windbg-command-line-preview) it says that the following command should log the output to a file:
WinDbgX.exe logo ".myfile.txt"
However the windbg tells me that the debugger cannot find the file specified. I did run the command from powershell where myfile.txt is located so im not sure what the correct syntax is. I also tried other variants such as:
WinDbgX.exe "logo .aaa.txt"
I also tried passing the parameter after specifying a particular imagine file to debug:
windbgx.exe myapp.exe logo myfile.txt
powershell cmd windbg
powershell cmd windbg
asked Nov 25 '18 at 1:57
mblmbl
6818
asked Nov 25 '18 at 1:57
mblmbl
6818
asked Nov 25 '18 at 1:57
mblmbl
6818
asked Nov 25 '18 at 1:57
mblmbl
6818
asked Nov 25 '18 at 1:57
mblmbl
6818
6818
Is that something powershell specific? Can you run it in cmd?
– Mike Twc
Nov 25 '18 at 2:32
It's not. I also tried from cmd.
– mbl
Nov 25 '18 at 2:37
Did you tried full path of the file? I think "." will be a working directory of windbg, not powershell's
– Mike Twc
Nov 25 '18 at 2:42
From PS I tried: WinDbgX.exe .myapp.exe logo "C:UsersmynameDesktopaaa.txt" and I don't get an error anymore. However nothing is logged to my text file after I break into my program and use some debugger commands just to test. The first line of the command window that appears when the debugger launch is this: CommandLine: .myapp.exe logo C:UsersmynameDesktopaaa.txt
– mbl
Nov 25 '18 at 2:50
1
Possible typo in the documentation. Try-logowith a leading hyphen. Without the hyphen, it looks like you're trying to debug a program calledlogo.
– Raymond Chen
Nov 25 '18 at 4:13
|
show 4 more comments
Is that something powershell specific? Can you run it in cmd?
– Mike Twc
Nov 25 '18 at 2:32
It's not. I also tried from cmd.
– mbl
Nov 25 '18 at 2:37
Did you tried full path of the file? I think "." will be a working directory of windbg, not powershell's
– Mike Twc
Nov 25 '18 at 2:42
From PS I tried: WinDbgX.exe .myapp.exe logo "C:UsersmynameDesktopaaa.txt" and I don't get an error anymore. However nothing is logged to my text file after I break into my program and use some debugger commands just to test. The first line of the command window that appears when the debugger launch is this: CommandLine: .myapp.exe logo C:UsersmynameDesktopaaa.txt
– mbl
Nov 25 '18 at 2:50
1
Possible typo in the documentation. Try-logowith a leading hyphen. Without the hyphen, it looks like you're trying to debug a program calledlogo.
– Raymond Chen
Nov 25 '18 at 4:13
Is that something powershell specific? Can you run it in cmd?
– Mike Twc
Nov 25 '18 at 2:32
Is that something powershell specific? Can you run it in cmd?
– Mike Twc
Nov 25 '18 at 2:32
It's not. I also tried from cmd.
– mbl
Nov 25 '18 at 2:37
It's not. I also tried from cmd.
– mbl
Nov 25 '18 at 2:37
Did you tried full path of the file? I think "." will be a working directory of windbg, not powershell's
– Mike Twc
Nov 25 '18 at 2:42
Did you tried full path of the file? I think "." will be a working directory of windbg, not powershell's
– Mike Twc
Nov 25 '18 at 2:42
From PS I tried: WinDbgX.exe .myapp.exe logo "C:UsersmynameDesktopaaa.txt" and I don't get an error anymore. However nothing is logged to my text file after I break into my program and use some debugger commands just to test. The first line of the command window that appears when the debugger launch is this: CommandLine: .myapp.exe logo C:UsersmynameDesktopaaa.txt
– mbl
Nov 25 '18 at 2:50
From PS I tried: WinDbgX.exe .myapp.exe logo "C:UsersmynameDesktopaaa.txt" and I don't get an error anymore. However nothing is logged to my text file after I break into my program and use some debugger commands just to test. The first line of the command window that appears when the debugger launch is this: CommandLine: .myapp.exe logo C:UsersmynameDesktopaaa.txt
– mbl
Nov 25 '18 at 2:50
1
1
Possible typo in the documentation. Try
-logo with a leading hyphen. Without the hyphen, it looks like you're trying to debug a program called logo.– Raymond Chen
Nov 25 '18 at 4:13
Possible typo in the documentation. Try
-logo with a leading hyphen. Without the hyphen, it looks like you're trying to debug a program called logo.– Raymond Chen
Nov 25 '18 at 4:13
|
show 4 more comments
1 Answer
1
active
oldest
votes
The log options seem to be unavailable in WinDbg Preview (WinDbgX) version 1.0.1810.02001, as well as some others like /update.
Even /? and -? do not display the list of available commands. Instead it runs invisible with 100% CPU on one logical core.
As an alternative, run -c ".logopen myfile.txt" to open a log file at the initial breakpoint.
The "old" WinDbg (non-Preview) uses -logo with a hyphen. Since you tried WinDbgX.exe .myapp.exe -logo "C:UsersmynameDesktopaaa.txt, let me note that the executable needs to be the last parameter on the WinDbg command line.
If you pass anything behind the executable, that will be passed as parameters to that executable:
executable
Specifies the command line of an executable process. This is used to launch a new process and debug it. This has to be the final item on the command line. All text after the executable name is passed to the executable as its argument string.
answered Nov 25 '18 at 18:29
Thomas WellerThomas Weller
28.8k1066137
This makes sense to me, however I just triedWinDbgX.exe -logo "C:UsersmynameDesktopaaa.txt" "C:Usersmynamemyapp.exe"and when windbg opens I get the errorCouldn't process command line parameters: Unrecognized command line option: logo
– mbl
Nov 25 '18 at 18:48
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53464035%2fhow-to-log-windbgx-exe-output-to-a-file%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
The log options seem to be unavailable in WinDbg Preview (WinDbgX) version 1.0.1810.02001, as well as some others like /update.
Even /? and -? do not display the list of available commands. Instead it runs invisible with 100% CPU on one logical core.
As an alternative, run -c ".logopen myfile.txt" to open a log file at the initial breakpoint.
The "old" WinDbg (non-Preview) uses -logo with a hyphen. Since you tried WinDbgX.exe .myapp.exe -logo "C:UsersmynameDesktopaaa.txt, let me note that the executable needs to be the last parameter on the WinDbg command line.
If you pass anything behind the executable, that will be passed as parameters to that executable:
executable
Specifies the command line of an executable process. This is used to launch a new process and debug it. This has to be the final item on the command line. All text after the executable name is passed to the executable as its argument string.
answered Nov 25 '18 at 18:29
Thomas WellerThomas Weller
28.8k1066137
This makes sense to me, however I just triedWinDbgX.exe -logo "C:UsersmynameDesktopaaa.txt" "C:Usersmynamemyapp.exe"and when windbg opens I get the errorCouldn't process command line parameters: Unrecognized command line option: logo
– mbl
Nov 25 '18 at 18:48
add a comment |
The log options seem to be unavailable in WinDbg Preview (WinDbgX) version 1.0.1810.02001, as well as some others like /update.
Even /? and -? do not display the list of available commands. Instead it runs invisible with 100% CPU on one logical core.
As an alternative, run -c ".logopen myfile.txt" to open a log file at the initial breakpoint.
The "old" WinDbg (non-Preview) uses -logo with a hyphen. Since you tried WinDbgX.exe .myapp.exe -logo "C:UsersmynameDesktopaaa.txt, let me note that the executable needs to be the last parameter on the WinDbg command line.
If you pass anything behind the executable, that will be passed as parameters to that executable:
executable
Specifies the command line of an executable process. This is used to launch a new process and debug it. This has to be the final item on the command line. All text after the executable name is passed to the executable as its argument string.
answered Nov 25 '18 at 18:29
Thomas WellerThomas Weller
28.8k1066137
This makes sense to me, however I just triedWinDbgX.exe -logo "C:UsersmynameDesktopaaa.txt" "C:Usersmynamemyapp.exe"and when windbg opens I get the errorCouldn't process command line parameters: Unrecognized command line option: logo
– mbl
Nov 25 '18 at 18:48
add a comment |
The log options seem to be unavailable in WinDbg Preview (WinDbgX) version 1.0.1810.02001, as well as some others like /update.
Even /? and -? do not display the list of available commands. Instead it runs invisible with 100% CPU on one logical core.
As an alternative, run -c ".logopen myfile.txt" to open a log file at the initial breakpoint.
The "old" WinDbg (non-Preview) uses -logo with a hyphen. Since you tried WinDbgX.exe .myapp.exe -logo "C:UsersmynameDesktopaaa.txt, let me note that the executable needs to be the last parameter on the WinDbg command line.
If you pass anything behind the executable, that will be passed as parameters to that executable:
executable
Specifies the command line of an executable process. This is used to launch a new process and debug it. This has to be the final item on the command line. All text after the executable name is passed to the executable as its argument string.
answered Nov 25 '18 at 18:29
Thomas WellerThomas Weller
28.8k1066137
The log options seem to be unavailable in WinDbg Preview (WinDbgX) version 1.0.1810.02001, as well as some others like /update.
Even /? and -? do not display the list of available commands. Instead it runs invisible with 100% CPU on one logical core.
As an alternative, run -c ".logopen myfile.txt" to open a log file at the initial breakpoint.
The "old" WinDbg (non-Preview) uses -logo with a hyphen. Since you tried WinDbgX.exe .myapp.exe -logo "C:UsersmynameDesktopaaa.txt, let me note that the executable needs to be the last parameter on the WinDbg command line.
If you pass anything behind the executable, that will be passed as parameters to that executable:
executable
Specifies the command line of an executable process. This is used to launch a new process and debug it. This has to be the final item on the command line. All text after the executable name is passed to the executable as its argument string.
answered Nov 25 '18 at 18:29
Thomas WellerThomas Weller
28.8k1066137
edited Nov 25 '18 at 19:41
answered Nov 25 '18 at 18:29
Thomas WellerThomas Weller
28.8k1066137
answered Nov 25 '18 at 18:29
Thomas WellerThomas Weller
28.8k1066137
answered Nov 25 '18 at 18:29
Thomas WellerThomas Weller
28.8k1066137
28.8k1066137
This makes sense to me, however I just triedWinDbgX.exe -logo "C:UsersmynameDesktopaaa.txt" "C:Usersmynamemyapp.exe"and when windbg opens I get the errorCouldn't process command line parameters: Unrecognized command line option: logo
– mbl
Nov 25 '18 at 18:48
add a comment |
This makes sense to me, however I just triedWinDbgX.exe -logo "C:UsersmynameDesktopaaa.txt" "C:Usersmynamemyapp.exe"and when windbg opens I get the errorCouldn't process command line parameters: Unrecognized command line option: logo
– mbl
Nov 25 '18 at 18:48
This makes sense to me, however I just tried
WinDbgX.exe -logo "C:UsersmynameDesktopaaa.txt" "C:Usersmynamemyapp.exe" and when windbg opens I get the error Couldn't process command line parameters: Unrecognized command line option: logo – mbl
Nov 25 '18 at 18:48
This makes sense to me, however I just tried
WinDbgX.exe -logo "C:UsersmynameDesktopaaa.txt" "C:Usersmynamemyapp.exe" and when windbg opens I get the error Couldn't process command line parameters: Unrecognized command line option: logo – mbl
Nov 25 '18 at 18:48
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53464035%2fhow-to-log-windbgx-exe-output-to-a-file%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Is that something powershell specific? Can you run it in cmd?
– Mike Twc
Nov 25 '18 at 2:32
It's not. I also tried from cmd.
– mbl
Nov 25 '18 at 2:37
Did you tried full path of the file? I think "." will be a working directory of windbg, not powershell's
– Mike Twc
Nov 25 '18 at 2:42
From PS I tried: WinDbgX.exe .myapp.exe logo "C:UsersmynameDesktopaaa.txt" and I don't get an error anymore. However nothing is logged to my text file after I break into my program and use some debugger commands just to test. The first line of the command window that appears when the debugger launch is this: CommandLine: .myapp.exe logo C:UsersmynameDesktopaaa.txt
– mbl
Nov 25 '18 at 2:50
1
Possible typo in the documentation. Try
-logowith a leading hyphen. Without the hyphen, it looks like you're trying to debug a program calledlogo.– Raymond Chen
Nov 25 '18 at 4:13