From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4142 invoked by alias); 1 Jul 2005 18:26:46 -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 4128 invoked by uid 22791); 1 Jul 2005 18:26:42 -0000 Received: from relay03.pair.com (HELO relay03.pair.com) (209.68.5.17) by sourceware.org (qpsmtpd/0.30-dev) with SMTP; Fri, 01 Jul 2005 18:26:42 +0000 Received: (qmail 36931 invoked from network); 1 Jul 2005 18:26:40 -0000 Received: from unknown (HELO ?192.168.123.1?) (unknown) by unknown with SMTP; 1 Jul 2005 18:26:40 -0000 X-pair-Authenticated: 24.126.76.52 Message-ID: <42C588F5.4040704@kegel.com> Date: Fri, 01 Jul 2005 18:26:00 -0000 From: Dan Kegel User-Agent: Mozilla/4.0 (compatible;MSIE 5.5; Windows 98) MIME-Version: 1.0 To: gdb@sources.redhat.com Subject: gdb and glibc-2.2.2? Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2005-07/txt/msg00004.txt.bz2 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? (Looking at the rest of the diffs from glibc-2.2.2 onwards, though, I get the feeling that thread support was still very much a work in progress, so even if I get past this hurdle, I have a feeling the resulting debugging experience might not be so pleasant.) Thanks, Dan -- Trying to get a job as a c++ developer? See http://kegel.com/academy/getting-hired.html