Normally you do not need to access bug report:
EurekaLog 7.7.8.2
Application: ------------------------------------------------------- 1.1 Start Date : Wed, 17 Oct 2018 16:23:33 +0300 1.2 Name/Description: Project1.exe 1.3 Version Number : 1.4 Parameters : 1.5 Compilation Date: Wed, 17 Oct 2018 16:23:15 +0300 1.6 Up Time : 6 second(s)
Exception: ------------------------------------------------------------------------ 2.1 Date : Wed, 17 Oct 2018 16:23:39 +0300 2.2 Address : 012A03F0 2.3 Module Name : Project1.exe 2.4 Module Version: 2.5 Type : ERangeError 2.6 Message : Range check error at Unit1.Button1Click (Line 261) 2.7 ID : ABBB0630 2.8 Count : 1
...
It is sufficient to use one of the mentioned above usage cases.
However, one particular example of when you want to access a simple bug report is when you are migrating old code from EurekaLog 6. Bug report was removed from OnExceptionNotify event because bug report does not exist outside of exception processing in EurekaLog 7 (unlike EurekaLog 6). For example, if you decide not to handle exception in OnExceptionNotify event handler - then there will be no bug report generated at all, thus saving processing time.
If you still want EurekaLog 6 style behavior - then bug report content can be retrieved from Dialog.BugReport property at any time (which is basically a cache of LogBuilder.Report property). For example:
uses
In other words, you should replace your OnExceptionNotify event handler with OnEndReportGen event handler. This event handler will be called like this:
Alternatively, bug report can be created at any time (on demand) - by using BuildBugReport function:
uses // ... write bug report's content to your DB // or do whatever you want with it
See also:
|