EurekaLog supports reading of some 3rd party formats of debug information. This feature could be used in a migration scenario: when you migrate your multi-DLL project from other solution (such as JCL, madExcept, etc.) to EurekaLog. You can re-use old DLLs without recompiling these DLLs for EurekaLog. Your application should use the single exception tracer scheme.
You can mix EurekaLog-enabled DLLs and "3rd party-enabled DLLs" in the same application. In other words, EurekaLog-enabled DLLs with "DLL" profile (i.e. without exception tracer in DLL) are interchangeable with DLLs post-processed by 3rd party tools (without including a working exception tracer in DLL). "Standalone DLL" profile is not compatible with 3rd party exception tracers.
Host application should have ability to read debug information from DLLs. EurekaLog supports many formats of debug information. Support for EurekaLog's own format of debug information is always enabled. Other formats should be enabled manually in EurekaLog project's options.
Note: there is no support to convert debug information from 3rd party post-processor tools into EurekaLog debug information format. That's because all such formats are very similar to each other. There is no significant benefit from converting debug information from some debug information format to another format. Therefore you should just enable support for particular format in your application. No convertation is necessary.