Have the glibc build use the cross-objdump, rather than the host one.
On some distros (eg. Fedora), the native objdump can not interpret objects not for the native system, and thus fail.
This commit adds a new patch against glibc-2.7 that introduces OBJDUMP_FOR_HOST, wich, if set, overides the detected objdump.
Note: bizarely enough, glibc already has code to detect the cross-objdump, but that does not work for an unknown reason... :-(
/trunk/patches/glibc/2.7/220-objdump_for_host.patch | 13 13 0 0 +++++++++
/trunk/scripts/build/libc_glibc.sh | 37 21 16 0 +++++++++++++++------------
2 files changed, 34 insertions(+), 16 deletions(-)
1 --- gdb-6.3.org/gdb/gdbserver/thread-db.c 2004-10-17 02:42:00.000000000 +0900
2 +++ gdb-6.3/gdb/gdbserver/thread-db.c 2005-01-27 12:19:29.000000000 +0900
4 Foundation, Inc., 59 Temple Place - Suite 330,
5 Boston, MA 02111-1307, USA. */
10 #include "linux-low.h"
14 struct inferior_linux_data *tdata;
18 fprintf (stderr, "Thread creation event.\n");
20 In the LinuxThreads implementation, this is safe,
21 because all events come from the manager thread
22 (except for its own creation, of course). */
23 - err = td_ta_event_getmsg (thread_agent, &msg);
24 + for (timeout = 0; timeout < 50000; timeout++)
26 + err = td_ta_event_getmsg (thread_agent, &msg);
27 + if (err != TD_NOMSG)
32 fprintf (stderr, "thread getmsg err: %s\n",
33 thread_db_err_str (err));