https://bugs.kde.org/show_bug.cgi?id=511324
--- Comment #2 from Malte S. Stretz <[email protected]> --- Today I ran into another crash which triggered this issue and since it was reproducible I started adding some print()s to SentryTrace.load_solib() to see if there is something about the frame which would allow us to skip it. Long story short: I had some red herrings but couldn't really find anything to really identify this. The main issue is that there is no image found for the symbol. Could this be due to the binutils bug explained in https://sourceware.org/bugzilla/show_bug.cgi?id=32844 which is referenced somewhere else in the code? gdb itself can't decode the frame in question either, see below. I wonder though if instead of throwing an exception the script should just `continue`, assuming that the other frames still contain some useful information? > #0 __pthread_kill_implementation (no_tid=0, signo=11, threadid=<optimized > out>) at ./nptl/pthread_kill.c:44 > #1 __pthread_kill_internal (signo=11, threadid=<optimized out>) at > ./nptl/pthread_kill.c:78 > #2 __GI___pthread_kill (threadid=<optimized out>, signo=signo@entry=11) at > ./nptl/pthread_kill.c:89 > #3 0x000073f22a24527e in __GI_raise (sig=11) at ../sysdeps/posix/raise.c:26 > #4 0x000073f22e5def57 in KCrash::defaultCrashHandler (sig=11) at > /workspace/build/src/kcrash.cpp:623 > #5 <signal handler called> > #6 0x000073f2191f9590 in ?? () > #7 0x000073f22cd086ad in Exiv2::Image::setMetadata(Exiv2::Image const&) () > from /lib/x86_64-linux-gnu/libexiv2.so.27 > ... -- You are receiving this mail because: You are watching all bug changes.
