John McCabe-Dansted
Sat, 06 Mar 2010 05:31:58 -0800
On Fri, Mar 5, 2010 at 10:48 PM, Vincent van Ravesteijn - TNW <v.f.vanraveste...@tudelft.nl> wrote: > Did we leave the instability period that was expected due to: > - threaded export,
IMHO we should #define EXPORT_in_THREAD 0 I have done this in keytest since otherwise keytest would do almost nothing but generate reports about EXPORT_in_THREAD problems such as #6427. On my machine each threaded export has a roughly 50% chance of crashing LyX. We don't need users tell us that EXPORT_in_THREAD is broken. We already know it is. Another thing: will the alphas abort on assertions? We know that there are some mostly harmless assertions that popup without warning such as #6172 lassert.cpp(21): ASSERTION y > -1000000 VIOLATED IN CoordCache?.cpp:31 There seems to be little gain in triggering a SIGABRT on such assertions. If we do not want these assertions being buried in some xsession file no-one reads, perhaps we could modify LASSERT to popup a dialog like the following.: +-------------------------------------- | Warning: Assertion triggered +-------------------------------------- | The following assertion has been triggered. This is a bug in LyX. Please the the Bug reporting guide and report this bug.* | lassert.cpp(21): ASSERTION y > -1000000 VIOLATED IN CoordCache?.cpp:31 | | [ ] Do not show this warning again | | [Abort] [Ignore] +--------------------------------------- We could perhaps also add options like "Get backtrace without aborting", "Search for bug in LyX bugtracker", and maybe even "Report bug in LYX bug tracker". * Though we probably don't want users actually reporting this particular bug since we already know about it. -- http://www.lyx.org/trac/ticket/6427 http://www.lyx.org/trac/ticket/6172 -- John C. McCabe-Dansted