Segmentation fault in ThreadSanitizerOffline with JavaThreadSanitizer tests about data-race-test

[GoogleCodeExporter]

Speaking about ThreadSanitizer for Java its state is more like "unsupported" 
rather than "complete".
If you attach the log that you're passing to ts_offline we can check if there's 
a bug on the ts_offline side. However if the problem is in incorrect order of 
events generated by the instrumented code, it's unlikely that anyone is going 
to fix it anytime soon.

Original comment by [email protected] on 31 Jul 2012 at 3:10

[GoogleCodeExporter]

Thanks for your response.

Here's the log.

Original comment by [email protected] on 31 Jul 2012 at 4:53

Attachments:

• events.tar.gz

[GoogleCodeExporter]

The same problem on Mac OS X. Also tried with other test code - the same line 
is reported.

Original comment by [email protected] on 27 Sep 2012 at 5:48

[GoogleCodeExporter]

As there is some activity here, I've just wanted to mention:

Revision r2582 seems to be working ok, so I presume something was changed in 
the format used by ts_offline, which leads to these inconsistencies.

We are currently working on concurrency analysis for Android applications and 
since we couldn't use Java Thread Sanitizer directly (due to ASM and its 
dynamic bytecode generation) we've implemented trace generation (more or less 
consistent with JTsan) via BCEL in our instrumentation tool 
(http://code.google.com/p/coffee-machine/).

I understand that JTSan is no longer developed, but still our plans include 
trying to investigate Java Thread Sanitizer compatibility issues with current 
version of ts_offline. If we manage to resolve these issues, we'll gladly file 
a patch.

Original comment by [email protected] on 28 Sep 2012 at 2:28

[GoogleCodeExporter]

Confirm: r2582 version successfully parsed jtsan files 

Original comment by [email protected] on 29 Sep 2012 at 1:24