Balazs Kezes c14f1b0486 Build glibc with unwind tables ... Without debug symbols or this you cannot have reliable backtraces in gdb. For instance this is on a Raspberry Pi without the unwind tables: $ gcc -x c <(echo 'void abort(); int main() { abort(); }') $ gdb ./a.out <<< $'r\nbt' ... #1 0xb6eb2e44 in abort () from /usr/lib/libc.so.6 #2 0x00000020 in ?? () Backtrace stopped: previous frame identical to this frame (corrupt stack?) ... Here's with the unwind tables enabled: $ gcc -x c <(echo 'void abort(); int main() { abort(); }') $ gdb ./a.out <<< $'r\nbt' ... #1 0xb6eade44 in abort () from /usr/lib/libc.so.6 #2 0x000084e0 in main () ... The upside of the unwind tables compared to the debug symbols is that they don't take up a lot of space.		2014-02-15 22:21:23 +00:00
..
glibc-2.18-xattr-compat-hack.patch	core/glibc to 2.18-12	2014-01-08 15:03:12 +00:00
glibc.install	core/glibc to 2.19-2	2014-02-14 13:38:54 +00:00
local-soname-hack.diff	core/glibc fixes	2014-01-17 19:46:52 +00:00
locale-gen	core/glibc to 2.19-2	2014-02-14 13:38:54 +00:00
locale.gen.txt	Added toolchain components (gcc 4.5.1/glibc 2.12.1)	2011-01-05 00:28:59 -07:00
PKGBUILD	Build glibc with unwind tables	2014-02-15 22:21:23 +00:00