> Please advise, my vb6.exe is crashing on ntdll.dll when building
> executables
> .WinXP with all latest windows-updates applied.
> Windbg crash dump:
Unfortunately, all that debug info is mostly worthless. You're gonna have to
find out the line of code that's causing the crash and post that. If you
can't reproduce this in the IDE, then you'll have to temporarily (or maybe
permanently) add code into your program to help in narrowing down the code
that's causing the crash (for example, write to a log file when procedures
are entered and exited...when the log has an entered procedure but no exited
procedure, you know the crash occured in that procedure...from that point,
you can further add logging at the line level). Just guessing, but I'd bet
it's an API function you're calling incorrectly.
There's just not much anyone can probably assist with until you can post
source code.

Signature
Mike
theon - 04 Jul 2009 02:57 GMT
Hi Mike,
unfortunately this is vb6.exe (not my app) crashing on "writing executable"
time ,not running time.My solution is huge and has a lot of source files.
How can I find out on compiling which function vb6.exe crashing ?
There is no direct reference to ntdll.dll and error is not incorrect
binding but vb6.exe heap crash on compiling. I wonder if there is hotfix for
vb6.exe compiler/linker.
> > Please advise, my vb6.exe is crashing on ntdll.dll when building
> > executables
[quoted text clipped - 13 lines]
> There's just not much anyone can probably assist with until you can post
> source code.
argusy - 05 Jul 2009 05:39 GMT
> Hi Mike,
> unfortunately this is vb6.exe (not my app) crashing on "writing executable"
[quoted text clipped - 5 lines]
> binding but vb6.exe heap crash on compiling. I wonder if there is hotfix for
> vb6.exe compiler/linker.
I just had this sort of problem an hour ago!!
What the problem was
For I = 0 to 51: text10(i).height = 300: next I
There were only 12 text boxes!! somehow, just before compiling, I must have
accidently overwritten '11' with '51', but that's all it took to crash the .exe
compilation
The fix
I finally got to 'tools' 'options', 'general' and changed error trapping to
"break on all errors". I normally have this set on, but I've only just set up
this computer with VB6, and I didn't change the setting. Don't ask me why it
crashed the compile as I didn't think that would happen. It also hung the IDE
run, and that's when I started thinking about the error trapping. Once I fixed
that, the IDE ran properly, and the compile worked as well
It could be your fix. If it isn't :<, then at least you know one thing it isn't
Graham
theon - 04 Jul 2009 03:11 GMT
I cannot add log, because it's vb6.exe IDE crashing on writing my app to .exe .
vb6.exe running my application ok, but crashig on "writing executable".
Solution is huge and has a lot of source files.
How can I find out on writing which class/function it's crashing ?
> > Please advise, my vb6.exe is crashing on ntdll.dll when building
> > executables
[quoted text clipped - 13 lines]
> There's just not much anyone can probably assist with until you can post
> source code.
First, try clearing out the temp files. Second, during compiling or running,
VB calls any user controls or ActiveX to read property values. Do you have
any UserControl in your project? The Initialize and ReadProperties events
fires as far as I know, so check if you have any code there that might cause
errors and comment it out temporarily, such as subclassing code.
Nobody - 04 Jul 2009 18:32 GMT
Another thing that might interfere is Add-ins, so try to disable them all to
see if that helps. If you have a backup copy of the last version that
compiles fine, use WinMerge to see what changed between 2 projects, just
specify two folders and it will compare all files. Double clicking a file,
will show the changes in two windows, side by side. It's free and open
source:
http://en.wikipedia.org/wiki/WinMerge
http://winmerge.org