Release a GDB 7.2 2011.05 tarball and verify it works with our platform
Bug #787078 reported by
Zach Pfeffer
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Linaro Android |
Fix Released
|
Undecided
|
Jim Huang |
Bug Description
1. Release a tarball.
2. Test the tarball.
Original email:
The Linaro Toolchain Working Group is pleased to announce the release
of Linaro GDB 7.2.
Linaro GDB 7.2 2011.05-0 is the sixth release in the 7.2 series. Based
off the latest GDB 7.2, it includes a number of ARM-focused bug fixes.
This release fixes:
* LP: #615972 Neon registers missing in core files
* LP: #615978 Failure to software single-step into signal handler
* LP: #615996 gdb.cp/
The source tarball is available at:
https:/
More information on Linaro GDB is available at:
https:/
-- Michael
Changed in linaro-android: | |
assignee: | nobody → Jim Huang (jserv) |
status: | New → Confirmed |
To post a comment you must log in.
If we use the vanilla one, we would encounter a dependency problem on x86:
$ ldd /tmp/android- toolchain- eabi/bin/ arm-eabi- gdb
libncurses. so.5 => not found 0000)
libexpat. so.1 => not found 3000)
/lib64/ ld-linux- x86-64. so.2 (0x000000004000 0000)
libm.so.6 => /lib64/libm.so.6 (0x0000000040a4
libc.so.6 => /lib64/libc.so.6 (0x0000000040cc
That is because we didn't get libraries (libexpat) statically linked. We can refer to the hacks from Google's gdb-7.1.x .