From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26007 invoked by alias); 10 Sep 2003 00:34:15 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 25990 invoked from network); 10 Sep 2003 00:34:14 -0000 Received: from unknown (HELO baradas.org) (66.166.225.55) by sources.redhat.com with SMTP; 10 Sep 2003 00:34:14 -0000 Received: by baradas.org (Postfix, from userid 500) id 049E59899C; Tue, 9 Sep 2003 20:34:13 -0400 (EDT) From: Peter Barada To: drow@mvista.com Cc: pbarada@mail.wm.sps.mot.com, gdb@sources.redhat.com, libc-alpha@sources.redhat.com In-reply-to: <20030909213003.GA5878@nevyn.them.org> (message from Daniel Jacobowitz on Tue, 9 Sep 2003 17:30:03 -0400) Subject: Re: Trouble with gdbserver from gdb-5.3, glibc-2.3.2 on ppc32 References: <200309092031.h89KVsI30886@hyper.wm.sps.mot.com> <20030909212241.GA5521@nevyn.them.org> <20030909213003.GA5878@nevyn.them.org> Message-Id: <20030910003413.049E59899C@baradas.org> Date: Wed, 10 Sep 2003 00:34:00 -0000 X-SW-Source: 2003-09/txt/msg00131.txt.bz2 > > I'm trying to bring up gdbserver2 on an ppc32 embedded linux platform, and > > What's gdbserver2? I'll just quietly assume you mean gdbserver... Duh. I have two versions of gdbserver around, won back from gdb-41.7 that I went through massive pains to get to build , and a newer one from gdb-5.3. > Read the source of libthread_db? No, really. Then start another > gdbserver debugging gdbserver, and step through td_ta_new. It fetches > the version. This could be a symptom of symbol lookup being messed up, > that's almost always the problem. Versions of the library on host and > target match? GDB found the rght target libraries? Uggh. Ok, I'll try this method(and add code to td_ta_new to dump why its tossing TD_VERSION). I believe that the versions have to match since I copy the librairs from the cross-compiled toolchain into the target's /lib directory; how they can differ isn't obvious to me. I would have thought that building up a toolchain using Dan's crosstool script would get me what I want. I read the description of solib-absolute-prefix, but it doesn't shed much light on why the *target* is complaining. I don't see in the remote protocol how it can ask for a particular library, so I'll dig depper and then get back to the mailing list. But back to my original(and probably stupid) question. Is there any way to extract information(using readelf, ldd, etc) to determine the version of the cross-built libpthread.so and libthread_db.so libraries? -- Peter Barada peter@baradas.org