Root > Solving bugs in your code > Logging


Previous pageReturn to chapter overviewNext page   

Often you need to collect additional data in order to successfully identify the bug in your application. You write ("log") additional useful information (events) into a single file ("log"), which is then attached to bug report. It is called "logging" (the act of keeping a log).


There are two engines in EurekaLog which you may use for logging purposes:

Routines in EMemLeaks unit can be used to mark (name) objects and other memory blocks. This is useful for memory leaks and other memory problems (name can help to identify object or otherwise anonymous memory block).
Routines in ELogging unit can be used to log any data into a single log file. This is useful to get idea of overall flow of your application.


Alternatively, you may use 3rd party logging frameworks.



See also:

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