<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">The function name and the line number may change if the code changes. A unique tag associated with the assertion should stay the same. So when you want to search for the assertion, you just need the tag since it is unique. We can even extend the dump to do the search in Bugzilla as well. So if the assertion fires, the dump might look like the following:<div class=""><br class=""></div><div class=""><div class=""><span class="Apple-tab-span" style="white-space: pre;"> </span>ASSERTION FAILED (tag: abcde) <i class="">condition</i></div><div class=""><span class=""> Bug 12345 (closed): </span>ASSERTION failed in someFunction</div><div class=""><span class=""> Bug 67890 (open): Still </span>ASSERTION failed in someFunction</div><div class=""><i class=""><span class="Apple-tab-span" style="white-space: pre;"> </span>… rest of the call-stack</i></div></div><div class=""><i class=""><br class=""></i></div><div class=""><span class="">So you do not even need to search Bugzilla for it. You would know immediately that the assertion is being tracked by an opened bug.</span></div></body></html>