From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9674 invoked by alias); 1 Jul 2005 18:34:03 -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 9652 invoked by uid 22791); 1 Jul 2005 18:34:00 -0000 Received: from relay00.pair.com (HELO relay.pair.com) (209.68.1.20) by sourceware.org (qpsmtpd/0.30-dev) with SMTP; Fri, 01 Jul 2005 18:34:00 +0000 Received: (qmail 73449 invoked from network); 1 Jul 2005 18:33:58 -0000 Received: from unknown (HELO ?192.168.123.1?) (unknown) by unknown with SMTP; 1 Jul 2005 18:33:58 -0000 X-pair-Authenticated: 24.126.76.52 Message-ID: <42C58AAA.9060405@kegel.com> Date: Fri, 01 Jul 2005 18:34:00 -0000 From: Dan Kegel User-Agent: Mozilla/4.0 (compatible;MSIE 5.5; Windows 98) MIME-Version: 1.0 To: Dan Kegel CC: gdb@sources.redhat.com Subject: Re: gdb and glibc-2.2.2? References: <42C588F5.4040704@kegel.com> In-Reply-To: <42C588F5.4040704@kegel.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2005-07/txt/msg00005.txt.bz2 Dan Kegel wrote: > What's the best version of gdb / gdbserver to use with > glibc-2.2.2? I'm hoping the latest gdb is ok. > > I'm finally adding gdb support to my toolchain build script. > Being greedy, I'm trying the latest gdb, even when building > with old versions of glibc. In particular, I'm trying > to build gdb-6.3 and its gdbserver against glibc-2.2.2. > Building gdbserver fails with > > thread-db.o(.text+0x43e): In function `thread_db_init': > gcc-3.4.4-glibc-2.2.2/gdb-6.3/gdb/gdbserver/thread-db.c:323: undefined > reference to `td_symbol_list' > thread-db.o(.text+0x443):gcc-3.4.4-glibc-2.2.2/gdb-6.3/gdb/gdbserver/thread-db.c:326: > undefined reference to `td_symbol_list' > > because td_symbol_list was added only as of glibc-2.2.3. > Now, td_symbol_list is a pretty simple function, and > is probably easy to backport. I'll probably give that a shot, > and build gdbserver static (since my glibc with the > td_symbol_list backport won't get installed on the target). > Sound reasonable? Or, maybe I'll take the lame way out, and just not build gdbserver for glibc < 2.2.3. Native gdb is what developers usually prefer anyway, given enough ram... but the question about which gdb is recommended for glibc-2.2.2 systems still stands. - Dan -- Trying to get a job as a c++ developer? See http://kegel.com/academy/getting-hired.html