Changes between Version 11 and Version 12 of FrequentlyAskedQuestions

Timestamp:

01/11/11 14:05:54 (2 years ago)

Author:

salcock

Comment:

Updated FAQ for threading bug

FrequentlyAskedQuestions

@@ -15 +15 @@
 
 === When using libtrace 3.0.7 or 3.0.8, I get a segmentation fault whenever I try to read a trace file! ===
-There appears to be a nasty threading bug that can crop up when libtrace is built with gcc 4.4.1 (which is the packaged version on many Ubuntu systems). 
+There appears to be a nasty threading bug that can crop up when libtrace is built with optimisations on a 32-bit system.
 
- * The best possible fix (until libtrace 3.0.9 is released) is to make the change described in r1681 and re-build libtrace. Obviously this will involve editing the libtrace source code but will fix the problem without impacting on performance.
+ * One possible fix (until libtrace 3.0.9 is released) is to make the change described in r1681 and re-build libtrace. Obviously this will involve editing the libtrace source code but will fix the problem without impacting on performance.
  * An alternative is to disable threaded IO by running 'export LIBTRACEIO=nothreads' in the terminal which you are using to run the failing libtrace program. This will disable threaded IO, which will make the trace processing slower.
  * You could also disable optimisations by adding 'CFLAGS="-g -O0"' when running ./configure - this will mean that you can still use threaded IO but the entirety of libtrace will be unoptimised. 
 
+UPDATE: the root cause has now been identified and fixed in r1685. Anyone seriously affected by this bug can email us at contact@wand.net.nz and we can provide a pre-release version of libtrace 3.0.9 that includes the fix.