Segmentation fault under certain conditions
damianw opened this issue · 1 comments
damianw commented
I am experiencing a segmentation fault when running nanoscope on a particular screen of my app. I'm not sure what's unique about this screen, but it's reliably reproducible.
backtrace:
#00 pc 0000000000486f28 /system/lib64/libart.so (_ZN3art12PrettyMethodEPNS_9ArtMethodEb+64)
#01 pc 0000000000457eb8 /system/lib64/libart.so (_ZN3art16flush_trace_dataENSt3__112basic_stringIcNS0_11char_traitsIcEENS0_9allocatorIcEEEEPlS7_PmS8_S8_S8_+2240)
#02 pc 000000000046d0e0 /system/lib64/libart.so (_ZNSt3__114__thread_proxyINS_5tupleIJPFvNS_12basic_stringIcNS_11char_traitsIcEENS_9allocatorIcEEEEPlS8_PmS9_S9_S9_ES7_S8_S8_S9_S9_S9_S9_EEEEEPvSD_+164)
#03 pc 0000000000068734 /system/lib64/libc.so (_ZL15__pthread_startPv+208)
#04 pc 000000000001da7c /system/lib64/libc.so (__start_thread+16)
I can supply the tombstone if necessary, although I think I would need to verify that there's no compromising information in the dump?
Leland-Takamine commented
Looks like it's failing when trying to grab the name of a method. I would be able to debug with sample code that reproduces this issue. My initial guess is the method in question is unique in some way.