HEAP[VB6.EXE]: Heap block at 0451DFB8 modified at 04521135 past requested
size of 3175
(14c8.c10): Break instruction exception - code 80000003 (first chance)
eax=0451dfb8 ebx=04521135 ecx=7c91ead5 edx=0013e5d7 esi=0451dfb8 edi=00003175
eip=7c90120e esp=0013e7d8 ebp=0013e7dc iopl=0 nv up ei pl nz na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000202
ntdll!DbgBreakPoint:
7c90120e cc int 3
Missing image name, possible paged-out or corrupt data.
Missing image name, possible paged-out or corrupt data.
Missing image name, possible paged-out or corrupt data.
0:000> k
ChildEBP RetAddr
0013e7d4 7c96e139 ntdll!DbgBreakPoint
0013e7dc 7c95f38c ntdll!RtlpBreakPointHeap+0x28
0013e7f4 7c96e507 ntdll!RtlpCheckBusyBlockTail+0x76
0013e808 7c96f75e ntdll!RtlpValidateHeapEntry+0xa4
0013e87c 7c94bc4c ntdll!RtlDebugFreeHeap+0x97
0013e964 7c927573 ntdll!RtlFreeHeapSlowly+0x37
0013ea34 004791b1 ntdll!RtlFreeHeap+0xf9
0013ea60 00535a15 vb6!ErrLoadPropArrayElements+0x13c
0013ea88 0041c12b vb6!COMBO::LoadProp+0xa8
0013ead8 0041b00f vb6!ProcessPropArray+0x25b
0013ec54 0041a805 vb6!CioReadTextProperties+0x703
0013eda4 0041a573 vb6!ProcessTextControlBlock+0x197
0013edd4 0041a5f8 vb6!CioReadTextControls+0x2b
0013ee04 0041a5f8 vb6!CioReadTextControls+0xb0
0013ee34 0041a5f8 vb6!CioReadTextControls+0xb0
0013ee64 0041a5f8 vb6!CioReadTextControls+0xb0
0013ee94 0041a5f8 vb6!CioReadTextControls+0xb0
0013eec4 0041a5f8 vb6!CioReadTextControls+0xb0
0013eef4 0041a5f8 vb6!CioReadTextControls+0xb0
0013ef24 0041a3c9 vb6!CioReadTextControls+0xb0
"theon" <th...@discussions.microsoft.com> wrote in message
news:4BEF32D9-C220-4C26...@microsoft.com...
> 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.
--
Mike
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.
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