Comment 26 for bug 1508767

This is another bug that produces segvs on power8 (could be related, not sure yet):
https://bugzilla.redhat.com/show_bug.cgi?id=1180633

I was able to reproduce this on wily/4.2 ppc64el machine trivially, and got the following output:
gcc -g test.c -O2 -o test -fgnu-tm -lpthread
ulimit -c unlimited
while ./test ; do :; done

Segmentation fault (core dumped)

[13861.517681] test[78415]: unhandled signal 11 at 0000000000000284 nip 000000001000ccc8 lr 000000001000d1c8 code 30001

(gdb) core ./core
[New LWP 78415]
[New LWP 78412]
[New LWP 78411]
[New LWP 78416]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/powerpc64le-linux-gnu/libthread_db.so.1".
Core was generated by `./test '.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x000000001000ccc8 in GTM::gtm_thread::trycommit() ()
[Current thread is 1 (Thread 0x3fff90cef040 (LWP 78415))]
(gdb) bt
#0 0x000000001000ccc8 in GTM::gtm_thread::trycommit() ()
#1 0x00003fff90cee600 in ?? ()
#2 0x0000000000000000 in ?? ()

;

However all this being said, a generic crash like this could happen from many different causes. Since we hit this with many packages could mean a shared library or compiler is causing the issue.

For the reported bug, can I please have core files produced from these crashes along with the exact binary version of the program that crashes? This way I can get some analysis similar to the above and start debugging.

Thanks,
--chris