------- Comment From [email protected] 2016-11-15 18:14 EDT------- Just got the following hit with the "distinct value in adapt_count" version of the library:
Thread 4 "python" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x3fff9b7cf1a0 (LWP 26828)] ... (gdb) x/i $pc => 0x3fffb5898df0 <_ZN10tensorflow12_GLOBAL__N_113ExecutorState8NodeDoneERKNS_6StatusEPKNS_4NodeERKNS_3gtl13InlinedVectorINS1_10TaggedNodeELi8EEEPNS_13NodeExecStatsEPNS1_20TaggedNodeReadyQueueE.constprop.432+208>: ld r9,104(r30) (gdb) info registers r30 r30 0x1111000000000000 Earlier we would often see that a NULL pointer on the stack was damaged to become 0x0001000000000000. Here we have that same scenario, but with the damage including the distinct value that the test code uses in adapt_count. So I'm confident it's at least an adapt_count store into an on-stack mutex that causing our crashes. Looks like a match. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1641241 Title: TensorFlow application crashes after glibc upgrade from 14.04 to 16.04 version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1641241/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
