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:
ASSERTION FAILED (tag: abcde) condition
Bug 12345 (closed): ASSERTION failed in someFunction
Bug 67890 (open): Still ASSERTION failed in someFunction
… rest of the call-stack
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.
_______________________________________________
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev