It works the same way as hooking APIs. Your hook callback function and "next hook" function variable need to have the same calling convention and parameters as the function you want to hook. Have you tried? Does it not work?
Of course I could offer such a service. However, there are situations where an application might crash in an endless loop and might then flood those services. Also, I'm not sure if my webserver is suited to handle the traffic/workload to cover all madExcept applications world-wide. So it's not overl...
In theory, madExcept should automatically activate the map file, because it's needed for Delphi projects. That is, if you compile within the IDE. If you compile outside of the IDE, you need to manually make sure that a detailed map file is created.
There's a "madTestMailAPIs.dpr" project, but I haven't updated it for more than 10 years, so I'm not sure if it's still useful to use. Probably not. You could copy madExcept.pas and mad.inc into your project folder and then set breakpoints in madExcept.pas to figure out what's going on. Al...
My recommendation would be to switch to HTTP upload instead, which usually is the most reliable bug report sending method. It does require you to put a proper PHP script on your webserver, though.
In BCB, the PE segments are much more complicated than in Delphi. So that's why I'm assuming this is probably specific to BCB. Maybe can you create a very simple test project which demonstrates the problem? The simpler, the better.
If I understand your code correctly, you're basically allocating a 1GB memory block via SetLength? That's very non-recommended to do. To be honest, I'm not fully sure why madExcept32.dll crashes, but generally, doing leak checking in 32bit adds a lot of RAM consumption on top of everything else, so ...