Comment 1 for bug 1338610

Unfortunately, apport-retrace thinks that all three of these crash reports have corrupt cores and don't provide useful backtraces. All of them show that /something/ called abort(), but the retrace fails before we get to the caller:

SourcePackage: indicator-location
Stacktrace:
 #0 0xb6b258e6 in ?? () from /lib/arm-linux-gnueabihf/libc.so.6
 No symbol table info available.
 #1 0xb6b3405e in raise () from /lib/arm-linux-gnueabihf/libc.so.6
 No symbol table info available.
 #2 0xb6b34d4e in abort () from /lib/arm-linux-gnueabihf/libc.so.6
 No symbol table info available.
 #3 0xb6c622b4 in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
 No symbol table info available.
 #4 0xb6c60af0 in ?? () from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
 No symbol table info available.
 Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Same for all three traces.

FWIW there's no direct call to abort(), assert(), g_error() in the indicator-location codebase, so the abort() call is coming from somewhere else in the stack.