PDA

View Full Version : access violation in exceptionlog.init


Ludek
24-Oct-2008, 08:14 AM
I'm getting strange errors with eurekalog-compiled exe. (6.0.17 and delphi 2009) It does not start on windows vista 32 bit. I tried remote debugging and I can see following in debug output:

... some loadings...
Module Load: LVPrcInj.dll. No Debug Info. Base Address: $02FB0000. Process XYZ.exe (6716)
Thread Exit: Thread ID: 7412. Process XYZ.exe (6716)
Debug Output: [ERROR] - Section: ExceptionLog.Init (Address: 01C4B4A0) - Address: 01C4B6BC - Message: "Access violation at address 01C4B6BC in module 'ABC.bpl'. Write of address 00000000" Process XYZ.exe (6716)

a very strange error unreadable error appears in the time on the remote station, with unreadable text and yes no.

if the user confirms it, i get next error:

Debug Output: [ERROR] - Section: ExceptionLog.Done (Address: 01C4BCE8) - Address: 7752B15F - Message: "Access violation at address 7752B15F in module 'ntdll.dll'. Write of address 00000014" Process XYZ.exe (6716)

the exe is very large, nearly 20 MB.

do you know, what could be happening there?

admin
29-Oct-2008, 09:10 AM
Hi Ludek,

try to do this:

1)...Close all opened Delphi/C++Builder instances;
2)...Deinstall all installed EurekaLog versions;
3)...Remove all folders containing the ExceptionLog.* or ?ExceptionExpert.* files;
4)...re-download and install the latest EurekaLog version;
5)...restart your PC.

I'm waiting to your feedback as soon as possible, OK? :)

If this did not works then try to create and send to me a little source demo able to reproduce your issue!

Ludek
29-Oct-2008, 09:33 AM
It happens on machines without delphi - so no instances could be opened, eurekalog is not installed at all, and there are no folders with exceptionlog.*. the computers have been restarted many times. I am unable to create a small demo, it happens only with a huge executable. But I could send you this executable if it helps ... (if you have vista 32 bit somewhere installed)

admin
03-Nov-2008, 08:43 AM
Hi Ludek,

try to re-download the last 6.0.17 version and rebuild your project with it.

I have just done some little changes in the 6.0.17 releases.

Ludek
03-Nov-2008, 11:39 AM
It still does not work. But it creates now following file:

Version : 6.0.17
Date : Fri, 24 Oct 2008 09:44:30 +0200
OS : Microsoft Windows Vista
RAD : BDS 6.0
Dump : $83 $40 $14 $01 $8B $5D $F4 $8B $7D $F0 $90 $80 $3D $82 $03 $FE $7F $00 $0F $85 $1F $B6 $03 $00 $8B $45 $FC $83 $F8 $FF $57 $6A
Section : ExceptionLog.Done (Address: 01C4BCE8)
LastExcept:
Address : $7752B15F - [774F0000] ntdll.dll - - - - 0[0]
Exception : EAccessViolation
Message : Access violation at address 7752B15F in module 'ntdll.dll'. Write of address 00000014
Call Stack:

Ludek
03-Nov-2008, 06:03 PM
Some new infos:
1. The previously mentioned file appears only occasionally.
2. If I compile with TD32-debug info, exe works
3. If I compile without FastMM FullDebugMode, exe works
4. If I compile without TD32-debug info and with FastMM FullDebugMode, exe in 95-99% does NOT work (the named exceptions in exception.init and done). but sometimes (typically after computer restart) the exe starts. next attempt to start the exe typically ends with a failure.

I have no idea what's happening there, because I don't have any sources - only pro version :(

Ludek
03-Nov-2008, 06:15 PM
more info:
under remote debugging, the exe creates a dialog "Probably internal bug" with some crazy text like "€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€" and two buttons yes and no. pressing "yes" tries to send an email. I didn't send anything, as my testing virtual machine has no email client installed.

Ludek
03-Nov-2008, 09:03 PM
last info for today :)
I have identified the line with the first access violation - it is the line 17891 in exceptionlog.pas, latest eurekalog 6.0.17, in "init".
instruction move byte ptr [eax], $00.
eax contains 0 and that makes the access violation.
I hope, this is enough for you to know, what's the bug :)

Ludek
06-Nov-2008, 12:16 PM
Is it really not enough? Do you need more to know? what exactly? I guess, it will solve also the other problem with application not initialized from Jokkey...

admin
07-Nov-2008, 10:38 AM
Hi Ludek,

I have just fixed this issue in the last released the 6.0.18 RC 2.

Try it and tell back to me your results, OK? :)

Ludek
07-Nov-2008, 11:51 AM
Yeaaah, I'll test it ASAP :)

Ludek
07-Nov-2008, 12:44 PM
Yesssss, now I'm having no problem starting on Vista 32bit any more.
thanks!

admin
07-Nov-2008, 01:35 PM
Hi Ludek,

perfect I'm really happy to read this!

PS: thank you for your detailed feedback! ;)