Root > Advanced topics > Using EurekaLog in DLL > DLLs post-processed by 3rd party tools (JCL, madExcept, etc.)

Using EurekaLog with DLLs post-processed by 3rd party tools (JCL, madExcept, etc.)

Previous pageReturn to chapter overviewNext page   

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.


1.Your host (.exe file) should be EurekaLog-enabled with enabled support for 4rd party debug information formats (see below).
2.Your DLL files could be:
oEurekaLog-enabled DLLs (using "Lightweight DLL profile")


oDLLs with 3rd party debug information which were post-processed by 3rd party compilers (such as JCL, madExcept, etc.)


You can mix EurekaLog-enabled DLLs and "3rd party-enabled DLLs" in the same application. In other words, EurekaLog-enabled DLLs with "Lightweight 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.



See also:

Send feedback... Build date: 2022-03-28
Last edited: 2019-06-17
The documentation team uses the feedback submitted to improve the EurekaLog documentation. We do not use your e-mail address for any other purpose. We will remove your e-mail address from our system after the issue you are reporting has been resolved. While we are working to resolve this issue, we may send you an e-mail message to request more information about your feedback. After the issues have been addressed, we may send you an email message to let you know that your feedback has been addressed.

Permanent link to this article: