Managing local bug reports by bug reports file rotation

EurekaLog can store bug reports locally - in a text file. This file is used both as a log and as a database. Each exception will be appended to the local bug report file. Some users want to know how to set up bug report file rotation. Log rotation is the automated process of managing log files to prevent them from growing too large, which can impact system performance and storage. It involves doing something with old log files (compressing, archiving, renaming, or deleting) and creating a new, empty one to continue recording new events.

This article will discuss what options you have for EurekaLog's local bug reports file.

What can you do with the "Assember" tab in bug reports? Is it even useful?

We were contacted by a customer that claimed that his application worked fine until he added EurekaLog to it. Specifically, his application starts to raise an EAccessViolation exception with the following message:
Access violation at address 03DB472F in module 'Sample.exe'. Read of address 5653E4CC

Does EurekaLog support CLang/LLVM/64-bit?

Short Answer

Yes, EurekaLog supports CLang and LLVM in both 32 and 64 bits - with some limitations. Exception is the very recent "Windows 64-bit (Modern)" platform, which was added into the RAD Studio 12 Athens since the major 12.1 update. The "Windows 64-bit (Modern)" platform is not supported yet.

EurekaLog causes EOutOfResources (Out of system resources)?

We were contacted by a person who complained that his application was working fine until he added EurekaLog to it. An "Out of system resources" exception was raised after adding EurekaLog to project. The exception occurred inside the OutOfResources helper function from the Vcl.Graphics unit.

EurekaLog causes Integer Overflow?

We were contacted by a person who complained that his application was working fine until he added EurekaLog to it. An Integer Overflow exception was raised after adding EurekaLog to project. The exception occurred inside the _UStrCatN function (it is a function for concatenating multiple strings in RTL).

EurekaLog causes AccessViolation?

We were contacted by a person who complained that his application was working fine until he added EurekaLog to it. An AccessViolation exception was raised after adding EurekaLog to project. The message was: "Access violation at address 00E15025 in module 'Project.exe'. Read of address 83EC8B69". And the stack was:

• Contoso.pas TContosoEventMessage.BasePerform
• Vcl.Forms.pas TApplication.WndProc
• System.Classes.pas StdWndProc
• Vcl.Forms.pas TApplication.HandleMessage
• Vcl.Forms.pas TApplication.Run
• Project.dpr Initialization

(all names have been replaced; Contoso represents some well-known library for Delphi).

Why is EurekaLog's call stack drawn in different colors?

Do you know what the different colors in the callstack mean?

New EurekaLog video tutorials available

We have published 3 new video tutorials:

How to read bug-reports

Well, recently I’ve noticed that there are many people, who have certain difficulties with reading and/or understanding bug-reports. There are many related questions both on support and forums. While it is quite surprising for me, it looks like there is a problem, which need to be solved.

Access Violation in details

Exception of class EAccessViolation is most common error in Delphi applications. Today I want to discuss it, its reasons and how to deal with it. This article is mostly for beginners, so it can contain not very accurate phrases.

Optimal project settings

Today I want to discuss various project's options, related to debugging.