On Mon, 17 Sep 2012 18:36:21 +0200
Vratislav Podzimek <vpodzime(a)redhat.com> wrote:
<snip>
The underlaying code raises an exception in a separate thread and
with a stack containing non-ascii characters (worst case scenario
designed from the bugs in exception handling seen so far). It also
produces a unique stack trace so that new bug is filed every time
exception handling and bug reporting in anaconda is tested.
Isn't that going to greatly increase the number of bugs filed against
anaconda and work against the duplicate detection in ABRT/libreport? I
didn't think that there were that many problems with improperly detected
duplicates.
These changes apply to the next build of anaconda (IIRC
anaconda-18.9-1).
Any guesses on when that build will be ready?
Tim