Many libraries/components are not tested for memory bugs

We were contacted by a customer, who claimed that EurekaLog causes Access Violation in a simple sample demo application.

Specifically, the application runs fine when compiled without EurekaLog and produces the expected results. But application crashes with "Access violation at address 00410759 in module 'DemoApp.exe'. Read of address 83EC8B59" when compiled with EurekaLog.

Support for FastMM 5 is available in EurekaLog

We are pleased to announce the availability of support for FastMM 5 in EurekaLog.

Memory problems in Delphi apps - final article

I've published several articles already, which cover different aspects of memory's issues. I'm going to give a short review of these articles first and then finish this series with current article. If you didn't read my previous articles or if you're a newbie - I recommend to read them from first to last before you'll start reading this one.

Catching memory leaks, redux

I tried to discuss things, that I've missed last time.

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.

Catching memory leaks

Before return to discussion of other ways to catch "bad" pointers - I wanted to talk about memory leaks and tools for its diagnostics. As we'll see later, this topic is very close related to our previous talk.

EurekaLog's anti-freeze feature

As you know, EurekaLog is a great tool to catch exceptions in your application. Though there are some cases which you want to consider as "bugs", but there is no exception to catch it!