Finally, I released version 1.0.5 of DDDebug - the Delphi memory tracker and exception handler - which supports Delphi 10 Seattle 32 and 64bit. Also, I continued my work for version 1.1 which will allow tracking of GDI, User and Kernel Objects in a user friendly manner. For more details take a look at

Post has attachment
Version 1.1 of DDDebug, the Delphi Memory Profiler, is about to be released during the next month. New features are the tracing of GDI, User and Kernel Objects to profile and observer resource allocations and leaks.

Post has attachment
We continue to reveal the potential of #Delphi #ORM 
Embarcadero MVP "plays" with #EntityDAC

Post has attachment
Some ‪#UniDAC‬ and ‪#MyDAC‬ tests in ‪#Android‬ from curious #Delphi developer

Post has attachment
How to develop a Mac OS X application in Delphi XE7 for work with SQL Server using SDAC  ->

Post has attachment
An update for the Delphi Memory Profiler DDDebug – Version – is available for download. This release fixes an odd bug, I have introduced lately, which prevents building the demo: the res file was not created. Furthermore, I have fixed a bug which resulted in the DDDebug main form being always reactivated and staying on top. On demand of some customers which are using MadExcept or EurekaLog, DDDebug can now use these libraries to resolve names of methods, so no MAP files are necessary or need to be distributed. A trial can be downloaded at

Post has attachment
 Version 1.0.1 of DDDebug - the Delphi Memory Profiler - has been released recently. Registered customers can download the update for free. In addition to some smaller enhancements, this release significantly improves the performance of the profiler. Read more about DDDebug and download a trial version at

+Eric Grange Can you please update your tool to support the most recent version of Delphi? If you don't own one then please ask someone that does (I do).
Thank you!

Running on Windows 8.1 no matter if as admin or not the "Attach to Process..." option is disabled. Why?

Access violation at address 004079AF in module 'SamplingProfiler.exe'. Read of address 0206F000.

I found this in version running in a Windows 7 VMWare guest. The executable being profiled was located in a folder on the host's drive shared with the VM using the VMWare's Shared Folders feature. To the guest it appears as a mapped network share.

Let me know if you need anymore information.
Wait while more posts are being loaded