Root > Reference > All Classes > TEurekaExceptionInfo > Properties > TEurekaExceptionInfo.BugID

Property TEurekaExceptionInfo.BugID

Previous pageReturn to chapter overviewNext page   

BugID value.






A hash that unique identifies exception.



This is a full BugID value.


BugID is a 4-byte unsigned integer (LongWord) which is used to identify exception. Two exception with the same BugID value are considered to be the same. BugID is used to establish uniqueness for many EurekaLog features (such as "Do not save duplicate exceptions", etc.). BugID is also used by EurekaLog Viewer tool when importing exceptions from multiple bug report files to eliminate duplicates. Two bug reports are considered to be duplicates of each other if they are bug reports about exceptions with the same BugID.


BugID consists of two parts. Hi-word is defined by EurekaLog. Lo-word is not used by EurekaLog and it's left for your customization.


Hi-word of BugID is a CRC16 value of string (" BugID ident") which includes application and module identification, exception class and two lines from call stack. "BugID ident" does not include exception message and exact error location (address). Only human-readable names are taken from call stack (unit name, class name and routine name). Thus, BugID will not change when you rebuild your application.


You can alter BugID (either by appending custom lo-word or fully replace it) in OnCustomBugID event handler.



It's not recommended to alter this value. Use CustomID to alter user part of BugID value.


Use BugIDStr to get human-readable string representation of BugID value.



See also

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