NTSD debugger

[sankar]

Hi I have a strange problem. I have an application in VC6.0 which makes use of crystal reports to generate a report. Now thi sapplication works fine in variuos systems under various OS. But , only in one machine ( to my badluck it happens to be the live machine ) this applciation crashes. there's o'cos no MSDEV & source code in that machine.and so, i used the NTSD debugger to get a little mor eknowledge on this and i got the following extract ( I have jus tpasted just a thte point of crsahing ) NTSD ModLoad: 77bc0000 77bc7000 RPCLTC1.dll NTSD: access violation NTSD: !!! second chance !!! eax=7469650a ebx=0000003f ecx=7469650a edx=0000003f esi=8c30cea6 edi=00000004 eip=7800d1c4 esp=0161fb7c ebp=0161fb98 iopl=0 nv up ei pl zr na po nc cs=001b ss=0023 ds=0023 es=0023 fs=0038 gs=0000 efl=00000246 *** WARNING: symbols checksum and timestamp is wrong 0x0004ed1e 0x000528d6 for m svcrt.dll MSVCRT!set_sbh_threshold+827: 7800d1c4 8906 mov [esi],eax ds:0023:8c30cea6=???????? 0:001> kb ChildEBP RetAddr Args to Child 0161fb98 7800cc1c 00901dc8 8c30cea6 0161fdd7 MSVCRT!set_sbh_threshold+0x827 0161fbdc 7800578c 0093320c 41104111 0093320c MSVCRT!set_sbh_threshold+0x27f 0161fbfc 4110bd0f 009337c0 00000002 00934e60 MSVCRT!_crtGetLocaleInfoW+0x580 0161fc30 4110bc2f 00934e60 0161fc5c 4110a7d6 P2SEVT+0xbd0f 0161fc3c 4110a7d6 00000001 00911170 00934e60 P2SEVT+0xbc2f 0161fc5c 42d6a1f7 009337e0 009337a0 009320a2 P2SEVT!SQLReadNextRecurringRecord+0 x8b 0161fe64 77e42257 005f0778 0000061c 00000000 CRAXDRT!DeleteUFLString+0x124c47 0161fe90 77f663f3 0161fea0 00000018 005f0778 USER32!IsWindow+0xa7 0161fee4 5f401301 00911364 00000000 00000000 ntdll!KiUserCallbackDispatcher+0x13 00911364 00000000 00000000 00000000 00000000 MFC42!Ordinal5307+0x13 Pl. let me know what does this mean . Thanks regards Sankar

[Tim Deveaux]

Looks like Crystal Reports (CRAXDRT)is crashing in a call to IsWindow() - hmmm... could be tricky... Its also telling you the symbol file for the MS C runtime is not the right one (which may be no big deal). Maybe take a look at all the dependencies in your exe and see if the versions of those DLLs are the same on the problem machine.