Root > Integral parts > Options > Bug report page > Bug report content page

Bug report content page

Previous pageReturn to chapter overviewNext page   

This is "Bug report content" page in EurekaLog project's options.

 

 

Bug report content options

 

Bug report content page specifies information to include into bug report. You can enable/disable information blocks here. See this article for more information about bug reports.

 

1. "Store this information in the bug report" (.soXYZ) option controls gathering of information in general section of bug report. These are generic information pieces, which mostly describes run-time environment. Only section two ("Exception") is specific to the problem.

 

You command EurekaLog to gather and include into report piece of information by checking checkbox on the left from this information name. Most options can be enabled and disabled, but there are few options, which are required and can't be disabled. These options are marked with "(*)".

 

"Select all" and "Unselect all" buttons can be used to quickly set/clear full selection.

 

Warning: your application may be considered as harmful (spy-ware) by customers, if it collects extensive information which is definitely non needed (like monitor information for non-GUI applications).

 

 

2. "Save stacks of EurekaLog-enabled threads" (.csoShowELThreads) option includes call stacks of all EurekaLog-enabled threads in application - regardless of thread type. By default only exception thread is captured.

 

"EurekaLog-enabled thread" term refers to thread with enabled per-thread EurekaLog. You can enable EurekaLog in any thread by calling SetEurekaLogStateInThread function or just simply create threads with TThreadEx or BeginThreadEx. See Enabling EurekaLog for background threads for more details.

 

Turn this option off for single-threaded application.

Turn this option on for multi-threaded application.

 

Note: capturing call stack of an external thread requires thread's suspending. In rare case this can cause deadlock issues (for example: thread may be suspended when it is running memory allocation function; thus, any further memory alloc/release operation will block application forever). Do not enable this option until really needed. See Using EurekaLog in multi-threaded applications for more details.

 

Taking call stack of additional threads will also require more time during exception processing.

 

Important Note: This option does NOT control if EurekaLog should automatically catch exceptions in threads. See multi-threading options.

 

 

3. "Save stacks of RTL threads" (.csoShowRTLThreads) option includes call stacks of all RTL threads in application. By default only exception thread is captured.

 

"RTL threads" means threads started with TThread or BeginThread.

 

It is recommended to keep this option off and use TThreadEx and BeginThreadEx or SetEurekaLogStateInThread together with "Save stacks of EurekaLog-enabled threads" option instead.

Turn this option on to capture call stack of external RTL threads (that is threads started by 3rd party code without your control).

 

Note: capturing call stack of an external thread requires thread's suspending. In rare case this can cause deadlock issues (for example: thread may be suspended when it is running memory allocation function; thus, any further memory alloc/release operation will block application forever). Do not enable this option until really needed. See Using EurekaLog in multi-threaded applications for more details.

 

Taking call stack of additional threads will require more time during exception processing.

 

Important Note: This option does NOT control if EurekaLog should automatically catch exceptions in threads. See multi-threading options.

 

 

4. "Save stacks of Windows threads" (.csoShowWindowsThreads) option includes call stacks of all non-RTL threads in application. By default only exception thread is captured.

 

"Windows threads" means threads started with CreateThread.

 

It is recommended to keep this option off and use TThreadEx and BeginThreadEx or SetEurekaLogStateInThread together with "Save stacks of EurekaLog-enabled threads" option instead. Alternatively, you may use "Save stacks of RTL threads" option instead.

Turn this option on to capture call stack of external Windows threads (that is threads started by 3rd party code without your control).

Never start your own thread with CreateThread function.

 

Note: capturing call stack of an external thread requires thread's suspending. In rare case this can cause deadlock issues (for example: thread may be suspended when it is running memory allocation function; thus, any further memory alloc/release operation will block application forever). Do not enable this option until really needed. See Using EurekaLog in multi-threaded applications for more details.

 

Taking call stack of additional threads will require more time during exception processing.

 

Important Note: This option does NOT control if EurekaLog should automatically catch exceptions in threads. See multi-threading options.

 

 

5. "Save modules list" (.loSaveModulesSection) option includes information about all loaded DLLs and BPLs ("modules") into bug report.

 

Note: this option is automatically disabled for reporting leaks.

 

 

6. "Save processes list" (.loSaveProcessesSection) option includes information about all running processes into bug report.

 

Note: this option is automatically disabled for reporting leaks.

 

 

7. "Save CPU information" (.loSaveAssemblerAndCPUSections) option includes information about CPU state (flags, registers, etc) and disassembly information in bug report. This option requires installed low-level hook.

 

Note: this option is automatically disabled for reporting leaks.

 

 

See also:

Bug report options page



Send feedback... Build date: 2020-10-22
Last edited: 2020-01-23
PRIVACY STATEMENT
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: https://www.eurekalog.com/help/eurekalog/bug_report_content_page.php