Root > Integral parts > Debug information providers > TD32


Previous pageReturn to chapter overviewNext page   

Turbo Debugger provider allows your application to extract information from TD32 debug information source. It can be external .tds file or injected information.


TD32 debug information is used by many debuggers. It's not required by Delphi/Builder IDE, but it's often used for interoperability reasons. It's de-facto standard for Pascal-based debuggers. TD32 contains not only names and line numbers, but also extensive information about variables, arguments, calling conventions and so on. However, EurekaLog uses only location information.


Use TD32 information when you want to use other debug tools which can understand TD32 format, but do not understand EurekaLog debug information format. Consider using EurekaLog debug format instead of TD32 format. TD32 format is extremely large (sometimes a x10 of original executable). They are binary files. There is no protection, no packing, no encryption. All debug information is stored in clear text.


You'll need to distribute .tds files with your application or you can inject TD32 information into executable (controlled by project options).


Note: It's highly recommended to convert .tds files to EurekaLog debug format. You are able to do such conversion without DLL recompilation as explained in this article.



See also:

Send feedback... Build date: 2022-03-28
Last edited: 2018-06-14
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: