madshi.net

Would be great, thank you very much. Yes I did, but it either disables the leak checking completely (as expected) or keeps on crashing if I specify LeakChecking for the specific build target. Using {$ifdef LeakChecking}, there are two dimensions/four scenarios: Deactivating Leak Checking with the ME...

Yes I did, but it either disables the leak checking completely (as expected) or keeps on crashing if I specify LeakChecking for the specific build target. I also searched to forum a little and found this topic: http://forum.madshi.net/viewtopic.php?f=4&t=28554&start=15 I guess this explains ...

Ok, this is strange .. I double checked it againl, but it doesn't crash with 2.8.8.0 for me. I'm compiling via IDE right now. The only difference in between the tests is the installed madExcept version. I can offer to share my screen with you if you want to take a closer look at the build environmen...

@Madshi: You are right, this issue is not specific for Delphi 10.4, but for MadCollection 2.8.8.99, which is required for Delphi 10.4. We are using this exact code with Delphi 10.3 and MadCollection 2.8.8.0 for years already, without a problem and (as far as I see) in accordance with the documentati...

Hi again! May I ask for an update on this again? Thank you!

Hello @madshi! Do you have any update on this already? I wouldn't want to push it, but some of our projects are currently failing (as they already started to migrate to Delphi 10.4, not knowing about this issue), and we would have plan whether to wait on a fix or to revert back to Delphi 10.3. Thank...

We usually activate the leak reporting for debug builds only, This allows us to test the application internally and publish a version without the check (as it is faster without the check and it would irritate most of the users more, than we would benefit from it). As the .mes file is the same for bo...

FWIW, you seem to be using either leak reporting or "instantly crash on buffer overrun", is that intentional? If you don't use either of these features, madExcept64.dll isn't used at all. Can you reproduce the problem with a simple test project? It took us a little to figure this one out,...

Hi, TOsEnum and COsDescr do not contain information for Windows Server 2016 yet and report such a system as Windows 10. The TOsVersionInfoExW.wProductType field is set to 3 (VER_NT_SERVER) and should provide the required indicator. (This was also used to patch TOSVersion with 10.2 Tokyo.) Additional...