Mixing
VB6 executable crashes intermittently in windows 8 and 10 - Have questions re WinDbg
I've debugged the code/compiler with WinDbg and it actually handled the exception. It seems to show the crash but I have no idea what the output means.
ModLoad: 72930000 72d35000 C:WINDOWSSysWOW64WININET.dll
(a38.cf0): Break instruction exception - code 80000003 (first chance)
eax=00000000 ebx=00000000 ecx=034b0000 edx=00000000 esi=003e2000
edi=7745d724
eip=774f80c9 esp=0019fa1c ebp=0019fa48 iopl=0 nv up ei pl zr na pe
nc cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b
efl=00000246
ntdll!LdrpDoDebuggerBreak+0x2b:
774f80c9 cc int 3
0:000> g
ModLoad: 03bd0000 03c56000 C:WINDOWSSysWOW64SXS.DLL
Any help in understanding and resolving this issue would be greatly appreciated.
Thanks,
exception vb6 windbg
asked Nov 19 '18 at 18:01
TaffmanTaffman
11
|
show 2 more comments
I've debugged the code/compiler with WinDbg and it actually handled the exception. It seems to show the crash but I have no idea what the output means.
ModLoad: 72930000 72d35000 C:WINDOWSSysWOW64WININET.dll
(a38.cf0): Break instruction exception - code 80000003 (first chance)
eax=00000000 ebx=00000000 ecx=034b0000 edx=00000000 esi=003e2000
edi=7745d724
eip=774f80c9 esp=0019fa1c ebp=0019fa48 iopl=0 nv up ei pl zr na pe
nc cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b
efl=00000246
ntdll!LdrpDoDebuggerBreak+0x2b:
774f80c9 cc int 3
0:000> g
ModLoad: 03bd0000 03c56000 C:WINDOWSSysWOW64SXS.DLL
Any help in understanding and resolving this issue would be greatly appreciated.
Thanks,
exception vb6 windbg
asked Nov 19 '18 at 18:01
TaffmanTaffman
11
That looks like a breakpoint. Post the error message in full. The number, the description, and the source or dll.
– CatCat
Nov 19 '18 at 20:08
2
ntdll!LdrpDoDebuggerBreak+0x2b: is the standard system breakpoint stop windbg has stopped after loading the process for you to examine this is the standard entry for all executables
– blabb
Nov 19 '18 at 20:22
Also you have to compile VB6 with no optimisations (else you won't recognise common assembly patterns and your function calls turn into unnamed inline code). There is a standard breakpoint at program entry and exit. Here is a little primer on WinDBG and VB6. stackoverflow.com/questions/52439321/…
– CatCat
Nov 19 '18 at 21:21
See Control PanelAll Control Panel ItemsSecurity and MaintenanceProblem Details and click your crash for details to post here.
– CatCat
Nov 19 '18 at 21:27
There are no errors, both the exe and the vb6 compiler crash to the desktop.
– Taffman
Nov 19 '18 at 22:00
|
show 2 more comments
I've debugged the code/compiler with WinDbg and it actually handled the exception. It seems to show the crash but I have no idea what the output means.
ModLoad: 72930000 72d35000 C:WINDOWSSysWOW64WININET.dll
(a38.cf0): Break instruction exception - code 80000003 (first chance)
eax=00000000 ebx=00000000 ecx=034b0000 edx=00000000 esi=003e2000
edi=7745d724
eip=774f80c9 esp=0019fa1c ebp=0019fa48 iopl=0 nv up ei pl zr na pe
nc cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b
efl=00000246
ntdll!LdrpDoDebuggerBreak+0x2b:
774f80c9 cc int 3
0:000> g
ModLoad: 03bd0000 03c56000 C:WINDOWSSysWOW64SXS.DLL
Any help in understanding and resolving this issue would be greatly appreciated.
Thanks,
exception vb6 windbg
asked Nov 19 '18 at 18:01
TaffmanTaffman
11
I've debugged the code/compiler with WinDbg and it actually handled the exception. It seems to show the crash but I have no idea what the output means.
ModLoad: 72930000 72d35000 C:WINDOWSSysWOW64WININET.dll
(a38.cf0): Break instruction exception - code 80000003 (first chance)
eax=00000000 ebx=00000000 ecx=034b0000 edx=00000000 esi=003e2000
edi=7745d724
eip=774f80c9 esp=0019fa1c ebp=0019fa48 iopl=0 nv up ei pl zr na pe
nc cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b
efl=00000246
ntdll!LdrpDoDebuggerBreak+0x2b:
774f80c9 cc int 3
0:000> g
ModLoad: 03bd0000 03c56000 C:WINDOWSSysWOW64SXS.DLL
Any help in understanding and resolving this issue would be greatly appreciated.
Thanks,
exception vb6 windbg
exception vb6 windbg
asked Nov 19 '18 at 18:01
TaffmanTaffman
11
asked Nov 19 '18 at 18:01
TaffmanTaffman
11
edited Nov 19 '18 at 19:39
Taffman
asked Nov 19 '18 at 18:01
TaffmanTaffman
11
asked Nov 19 '18 at 18:01
TaffmanTaffman
11
asked Nov 19 '18 at 18:01
TaffmanTaffman
11
11
That looks like a breakpoint. Post the error message in full. The number, the description, and the source or dll.
– CatCat
Nov 19 '18 at 20:08
2
ntdll!LdrpDoDebuggerBreak+0x2b: is the standard system breakpoint stop windbg has stopped after loading the process for you to examine this is the standard entry for all executables
– blabb
Nov 19 '18 at 20:22
Also you have to compile VB6 with no optimisations (else you won't recognise common assembly patterns and your function calls turn into unnamed inline code). There is a standard breakpoint at program entry and exit. Here is a little primer on WinDBG and VB6. stackoverflow.com/questions/52439321/…
– CatCat
Nov 19 '18 at 21:21
See Control PanelAll Control Panel ItemsSecurity and MaintenanceProblem Details and click your crash for details to post here.
– CatCat
Nov 19 '18 at 21:27
There are no errors, both the exe and the vb6 compiler crash to the desktop.
– Taffman
Nov 19 '18 at 22:00
|
show 2 more comments
That looks like a breakpoint. Post the error message in full. The number, the description, and the source or dll.
– CatCat
Nov 19 '18 at 20:08
2
ntdll!LdrpDoDebuggerBreak+0x2b: is the standard system breakpoint stop windbg has stopped after loading the process for you to examine this is the standard entry for all executables
– blabb
Nov 19 '18 at 20:22
Also you have to compile VB6 with no optimisations (else you won't recognise common assembly patterns and your function calls turn into unnamed inline code). There is a standard breakpoint at program entry and exit. Here is a little primer on WinDBG and VB6. stackoverflow.com/questions/52439321/…
– CatCat
Nov 19 '18 at 21:21
See Control PanelAll Control Panel ItemsSecurity and MaintenanceProblem Details and click your crash for details to post here.
– CatCat
Nov 19 '18 at 21:27
There are no errors, both the exe and the vb6 compiler crash to the desktop.
– Taffman
Nov 19 '18 at 22:00
That looks like a breakpoint. Post the error message in full. The number, the description, and the source or dll.
– CatCat
Nov 19 '18 at 20:08
That looks like a breakpoint. Post the error message in full. The number, the description, and the source or dll.
– CatCat
Nov 19 '18 at 20:08
2
2
ntdll!LdrpDoDebuggerBreak+0x2b: is the standard system breakpoint stop windbg has stopped after loading the process for you to examine this is the standard entry for all executables
– blabb
Nov 19 '18 at 20:22
ntdll!LdrpDoDebuggerBreak+0x2b: is the standard system breakpoint stop windbg has stopped after loading the process for you to examine this is the standard entry for all executables
– blabb
Nov 19 '18 at 20:22
Also you have to compile VB6 with no optimisations (else you won't recognise common assembly patterns and your function calls turn into unnamed inline code). There is a standard breakpoint at program entry and exit. Here is a little primer on WinDBG and VB6. stackoverflow.com/questions/52439321/…
– CatCat
Nov 19 '18 at 21:21
Also you have to compile VB6 with no optimisations (else you won't recognise common assembly patterns and your function calls turn into unnamed inline code). There is a standard breakpoint at program entry and exit. Here is a little primer on WinDBG and VB6. stackoverflow.com/questions/52439321/…
– CatCat
Nov 19 '18 at 21:21
See Control PanelAll Control Panel ItemsSecurity and MaintenanceProblem Details and click your crash for details to post here.
– CatCat
Nov 19 '18 at 21:27
See Control PanelAll Control Panel ItemsSecurity and MaintenanceProblem Details and click your crash for details to post here.
– CatCat
Nov 19 '18 at 21:27
There are no errors, both the exe and the vb6 compiler crash to the desktop.
– Taffman
Nov 19 '18 at 22:00
There are no errors, both the exe and the vb6 compiler crash to the desktop.
– Taffman
Nov 19 '18 at 22:00
|
show 2 more comments
1 Answer
1
active
oldest
votes
As i Commented what you have pasted in your query is the standard Starting point
for each and every executable that is loaded in windbg
you can load any executable and check it like this
C:Windows>cdb -c "q" nuget.exe | tail -4
ntdll!LdrpDoDebuggerBreak+0x2c: <<<<<<<<<<<<<<
77d805a6 cc int 3
0:000> cdb: Reading initial command 'q'
quit:
C:Windows>cdb -c "q" explorer.exe | tail -4
ntdll!LdrpDoDebuggerBreak+0x2c: <<<<<<<<<<<<
77d805a6 cc int 3
0:000> cdb: Reading initial command 'q'
quit:
C:Windows>cdb -c "q" bfsvc.exe | tail -4
ntdll!LdrpDoDebuggerBreak+0x2c: <<<<<<<<<<<
77d805a6 cc int 3
0:000> cdb: Reading initial command 'q'
quit:
C:Windows>
if you have a crash you need to provide the details of crash
please start a new thread or edit this query to add pertinent information
what you pasted are not the crash details
your application is probably crashing because of this
HEAP[Txxxxxxxh.exe]: HEAP: Free Heap block 0BA22450 modified at 0BA224B0 after it was freed
if windbg broke here look at the call stack using kb or run !analyze -v for pertinent info
what you uploaded contains mostly information output like module loads
and some spurious desktop window manager dlls (ms binary )debug output
which is of absolutely no use for analysing crash
please go through some basic tutorials on how to use windbg
answered Nov 19 '18 at 20:33
blabbblabb
5,1221920
Here's a link to the entire WinDbg output: drive.google.com/file/d/1itd5XbLF_TvMfdlOCP-oZbkJQFMtuT9y/…
– Taffman
Nov 19 '18 at 21:55
I compiled the code w/no optimizations and then ran WinDbg so there are 2 different logs for each of the exes
– Taffman
Nov 19 '18 at 22:22
sorry the file contains mostly debug outputs of module loads which are not crash details you probably have a delete() that is problematic you need to look at the call stack what you uploaded is of no use except for the single line which says that a free block is freed again
– blabb
Nov 19 '18 at 22:34
@Taffman - the easiest way to get a meaningfull dump is by using procdump and have it monitor your VB6 process for exceptions (second and/or first chance exceptions). Something like this started from the command line should do:procdump -ma -e 1 -n 100 -w vb6.exe. This will wait for a vb6.exe programm, attach and create maximum 100 dumpfiles for each exception thrown by vb6.
– Lieven Keersmaekers
Nov 20 '18 at 7:08
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%2f53380271%2fvb6-executable-crashes-intermittently-in-windows-8-and-10-have-questions-re-wi%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
As i Commented what you have pasted in your query is the standard Starting point
for each and every executable that is loaded in windbg
you can load any executable and check it like this
C:Windows>cdb -c "q" nuget.exe | tail -4
ntdll!LdrpDoDebuggerBreak+0x2c: <<<<<<<<<<<<<<
77d805a6 cc int 3
0:000> cdb: Reading initial command 'q'
quit:
C:Windows>cdb -c "q" explorer.exe | tail -4
ntdll!LdrpDoDebuggerBreak+0x2c: <<<<<<<<<<<<
77d805a6 cc int 3
0:000> cdb: Reading initial command 'q'
quit:
C:Windows>cdb -c "q" bfsvc.exe | tail -4
ntdll!LdrpDoDebuggerBreak+0x2c: <<<<<<<<<<<
77d805a6 cc int 3
0:000> cdb: Reading initial command 'q'
quit:
C:Windows>
if you have a crash you need to provide the details of crash
please start a new thread or edit this query to add pertinent information
what you pasted are not the crash details
your application is probably crashing because of this
HEAP[Txxxxxxxh.exe]: HEAP: Free Heap block 0BA22450 modified at 0BA224B0 after it was freed
if windbg broke here look at the call stack using kb or run !analyze -v for pertinent info
what you uploaded contains mostly information output like module loads
and some spurious desktop window manager dlls (ms binary )debug output
which is of absolutely no use for analysing crash
please go through some basic tutorials on how to use windbg
answered Nov 19 '18 at 20:33
blabbblabb
5,1221920
Here's a link to the entire WinDbg output: drive.google.com/file/d/1itd5XbLF_TvMfdlOCP-oZbkJQFMtuT9y/…
– Taffman
Nov 19 '18 at 21:55
I compiled the code w/no optimizations and then ran WinDbg so there are 2 different logs for each of the exes
– Taffman
Nov 19 '18 at 22:22
sorry the file contains mostly debug outputs of module loads which are not crash details you probably have a delete() that is problematic you need to look at the call stack what you uploaded is of no use except for the single line which says that a free block is freed again
– blabb
Nov 19 '18 at 22:34
@Taffman - the easiest way to get a meaningfull dump is by using procdump and have it monitor your VB6 process for exceptions (second and/or first chance exceptions). Something like this started from the command line should do:procdump -ma -e 1 -n 100 -w vb6.exe. This will wait for a vb6.exe programm, attach and create maximum 100 dumpfiles for each exception thrown by vb6.
– Lieven Keersmaekers
Nov 20 '18 at 7:08
add a comment |
As i Commented what you have pasted in your query is the standard Starting point
for each and every executable that is loaded in windbg
you can load any executable and check it like this
C:Windows>cdb -c "q" nuget.exe | tail -4
ntdll!LdrpDoDebuggerBreak+0x2c: <<<<<<<<<<<<<<
77d805a6 cc int 3
0:000> cdb: Reading initial command 'q'
quit:
C:Windows>cdb -c "q" explorer.exe | tail -4
ntdll!LdrpDoDebuggerBreak+0x2c: <<<<<<<<<<<<
77d805a6 cc int 3
0:000> cdb: Reading initial command 'q'
quit:
C:Windows>cdb -c "q" bfsvc.exe | tail -4
ntdll!LdrpDoDebuggerBreak+0x2c: <<<<<<<<<<<
77d805a6 cc int 3
0:000> cdb: Reading initial command 'q'
quit:
C:Windows>
if you have a crash you need to provide the details of crash
please start a new thread or edit this query to add pertinent information
what you pasted are not the crash details
your application is probably crashing because of this
HEAP[Txxxxxxxh.exe]: HEAP: Free Heap block 0BA22450 modified at 0BA224B0 after it was freed
if windbg broke here look at the call stack using kb or run !analyze -v for pertinent info
what you uploaded contains mostly information output like module loads
and some spurious desktop window manager dlls (ms binary )debug output
which is of absolutely no use for analysing crash
please go through some basic tutorials on how to use windbg
answered Nov 19 '18 at 20:33
blabbblabb
5,1221920
Here's a link to the entire WinDbg output: drive.google.com/file/d/1itd5XbLF_TvMfdlOCP-oZbkJQFMtuT9y/…
– Taffman
Nov 19 '18 at 21:55
I compiled the code w/no optimizations and then ran WinDbg so there are 2 different logs for each of the exes
– Taffman
Nov 19 '18 at 22:22
sorry the file contains mostly debug outputs of module loads which are not crash details you probably have a delete() that is problematic you need to look at the call stack what you uploaded is of no use except for the single line which says that a free block is freed again
– blabb
Nov 19 '18 at 22:34
@Taffman - the easiest way to get a meaningfull dump is by using procdump and have it monitor your VB6 process for exceptions (second and/or first chance exceptions). Something like this started from the command line should do:procdump -ma -e 1 -n 100 -w vb6.exe. This will wait for a vb6.exe programm, attach and create maximum 100 dumpfiles for each exception thrown by vb6.
– Lieven Keersmaekers
Nov 20 '18 at 7:08
add a comment |
As i Commented what you have pasted in your query is the standard Starting point
for each and every executable that is loaded in windbg
you can load any executable and check it like this
C:Windows>cdb -c "q" nuget.exe | tail -4
ntdll!LdrpDoDebuggerBreak+0x2c: <<<<<<<<<<<<<<
77d805a6 cc int 3
0:000> cdb: Reading initial command 'q'
quit:
C:Windows>cdb -c "q" explorer.exe | tail -4
ntdll!LdrpDoDebuggerBreak+0x2c: <<<<<<<<<<<<
77d805a6 cc int 3
0:000> cdb: Reading initial command 'q'
quit:
C:Windows>cdb -c "q" bfsvc.exe | tail -4
ntdll!LdrpDoDebuggerBreak+0x2c: <<<<<<<<<<<
77d805a6 cc int 3
0:000> cdb: Reading initial command 'q'
quit:
C:Windows>
if you have a crash you need to provide the details of crash
please start a new thread or edit this query to add pertinent information
what you pasted are not the crash details
your application is probably crashing because of this
HEAP[Txxxxxxxh.exe]: HEAP: Free Heap block 0BA22450 modified at 0BA224B0 after it was freed
if windbg broke here look at the call stack using kb or run !analyze -v for pertinent info
what you uploaded contains mostly information output like module loads
and some spurious desktop window manager dlls (ms binary )debug output
which is of absolutely no use for analysing crash
please go through some basic tutorials on how to use windbg
answered Nov 19 '18 at 20:33
blabbblabb
5,1221920
As i Commented what you have pasted in your query is the standard Starting point
for each and every executable that is loaded in windbg
you can load any executable and check it like this
C:Windows>cdb -c "q" nuget.exe | tail -4
ntdll!LdrpDoDebuggerBreak+0x2c: <<<<<<<<<<<<<<
77d805a6 cc int 3
0:000> cdb: Reading initial command 'q'
quit:
C:Windows>cdb -c "q" explorer.exe | tail -4
ntdll!LdrpDoDebuggerBreak+0x2c: <<<<<<<<<<<<
77d805a6 cc int 3
0:000> cdb: Reading initial command 'q'
quit:
C:Windows>cdb -c "q" bfsvc.exe | tail -4
ntdll!LdrpDoDebuggerBreak+0x2c: <<<<<<<<<<<
77d805a6 cc int 3
0:000> cdb: Reading initial command 'q'
quit:
C:Windows>
if you have a crash you need to provide the details of crash
please start a new thread or edit this query to add pertinent information
what you pasted are not the crash details
your application is probably crashing because of this
HEAP[Txxxxxxxh.exe]: HEAP: Free Heap block 0BA22450 modified at 0BA224B0 after it was freed
if windbg broke here look at the call stack using kb or run !analyze -v for pertinent info
what you uploaded contains mostly information output like module loads
and some spurious desktop window manager dlls (ms binary )debug output
which is of absolutely no use for analysing crash
please go through some basic tutorials on how to use windbg
answered Nov 19 '18 at 20:33
blabbblabb
5,1221920
edited Nov 19 '18 at 22:29
answered Nov 19 '18 at 20:33
blabbblabb
5,1221920
answered Nov 19 '18 at 20:33
blabbblabb
5,1221920
answered Nov 19 '18 at 20:33
blabbblabb
5,1221920
5,1221920
Here's a link to the entire WinDbg output: drive.google.com/file/d/1itd5XbLF_TvMfdlOCP-oZbkJQFMtuT9y/…
– Taffman
Nov 19 '18 at 21:55
I compiled the code w/no optimizations and then ran WinDbg so there are 2 different logs for each of the exes
– Taffman
Nov 19 '18 at 22:22
sorry the file contains mostly debug outputs of module loads which are not crash details you probably have a delete() that is problematic you need to look at the call stack what you uploaded is of no use except for the single line which says that a free block is freed again
– blabb
Nov 19 '18 at 22:34
@Taffman - the easiest way to get a meaningfull dump is by using procdump and have it monitor your VB6 process for exceptions (second and/or first chance exceptions). Something like this started from the command line should do:procdump -ma -e 1 -n 100 -w vb6.exe. This will wait for a vb6.exe programm, attach and create maximum 100 dumpfiles for each exception thrown by vb6.
– Lieven Keersmaekers
Nov 20 '18 at 7:08
add a comment |
Here's a link to the entire WinDbg output: drive.google.com/file/d/1itd5XbLF_TvMfdlOCP-oZbkJQFMtuT9y/…
– Taffman
Nov 19 '18 at 21:55
I compiled the code w/no optimizations and then ran WinDbg so there are 2 different logs for each of the exes
– Taffman
Nov 19 '18 at 22:22
sorry the file contains mostly debug outputs of module loads which are not crash details you probably have a delete() that is problematic you need to look at the call stack what you uploaded is of no use except for the single line which says that a free block is freed again
– blabb
Nov 19 '18 at 22:34
@Taffman - the easiest way to get a meaningfull dump is by using procdump and have it monitor your VB6 process for exceptions (second and/or first chance exceptions). Something like this started from the command line should do:procdump -ma -e 1 -n 100 -w vb6.exe. This will wait for a vb6.exe programm, attach and create maximum 100 dumpfiles for each exception thrown by vb6.
– Lieven Keersmaekers
Nov 20 '18 at 7:08
Here's a link to the entire WinDbg output: drive.google.com/file/d/1itd5XbLF_TvMfdlOCP-oZbkJQFMtuT9y/…
– Taffman
Nov 19 '18 at 21:55
Here's a link to the entire WinDbg output: drive.google.com/file/d/1itd5XbLF_TvMfdlOCP-oZbkJQFMtuT9y/…
– Taffman
Nov 19 '18 at 21:55
I compiled the code w/no optimizations and then ran WinDbg so there are 2 different logs for each of the exes
– Taffman
Nov 19 '18 at 22:22
I compiled the code w/no optimizations and then ran WinDbg so there are 2 different logs for each of the exes
– Taffman
Nov 19 '18 at 22:22
sorry the file contains mostly debug outputs of module loads which are not crash details you probably have a delete() that is problematic you need to look at the call stack what you uploaded is of no use except for the single line which says that a free block is freed again
– blabb
Nov 19 '18 at 22:34
sorry the file contains mostly debug outputs of module loads which are not crash details you probably have a delete() that is problematic you need to look at the call stack what you uploaded is of no use except for the single line which says that a free block is freed again
– blabb
Nov 19 '18 at 22:34
@Taffman - the easiest way to get a meaningfull dump is by using procdump and have it monitor your VB6 process for exceptions (second and/or first chance exceptions). Something like this started from the command line should do:
procdump -ma -e 1 -n 100 -w vb6.exe. This will wait for a vb6.exe programm, attach and create maximum 100 dumpfiles for each exception thrown by vb6.– Lieven Keersmaekers
Nov 20 '18 at 7:08
@Taffman - the easiest way to get a meaningfull dump is by using procdump and have it monitor your VB6 process for exceptions (second and/or first chance exceptions). Something like this started from the command line should do:
procdump -ma -e 1 -n 100 -w vb6.exe. This will wait for a vb6.exe programm, attach and create maximum 100 dumpfiles for each exception thrown by vb6.– Lieven Keersmaekers
Nov 20 '18 at 7:08
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2f53380271%2fvb6-executable-crashes-intermittently-in-windows-8-and-10-have-questions-re-wi%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
That looks like a breakpoint. Post the error message in full. The number, the description, and the source or dll.
– CatCat
Nov 19 '18 at 20:08
2
ntdll!LdrpDoDebuggerBreak+0x2b: is the standard system breakpoint stop windbg has stopped after loading the process for you to examine this is the standard entry for all executables
– blabb
Nov 19 '18 at 20:22
Also you have to compile VB6 with no optimisations (else you won't recognise common assembly patterns and your function calls turn into unnamed inline code). There is a standard breakpoint at program entry and exit. Here is a little primer on WinDBG and VB6. stackoverflow.com/questions/52439321/…
– CatCat
Nov 19 '18 at 21:21
See Control PanelAll Control Panel ItemsSecurity and MaintenanceProblem Details and click your crash for details to post here.
– CatCat
Nov 19 '18 at 21:27
There are no errors, both the exe and the vb6 compiler crash to the desktop.
– Taffman
Nov 19 '18 at 22:00