Comment #2 on issue 14589 by [email protected]: Crash in vsyscall http://code.google.com/p/chromium/issues/detail?id=14589
New insight! I got a stack from a user that has the following. Maybe we're failing to unwind when abort() was called. #0 0xffffe405 in __kernel_vsyscall () #1 0xf7312335 in raise () from /lib32/libc.so.6 #2 0xf7313cb1 in abort () from /lib32/libc.so.6 #3 0xf74fd820 in __gnu_cxx::__verbose_terminate_handler () from /usr/lib32/libstdc++.so.6 #4 0xf74fb0a5 in ?? () from /usr/lib32/libstdc++.so.6 #5 0xf74fb0e2 in std::terminate () from /usr/lib32/libstdc++.so.6 #6 0xf74fb9a5 in __cxa_pure_virtual () from /usr/lib32/libstdc++.so.6 and then into GTK. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
