From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31473 invoked by alias); 11 Oct 2004 17:22:06 -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 31364 invoked from network); 11 Oct 2004 17:22:04 -0000 Received: from unknown (HELO pippin.tausq.org) (64.81.244.94) by sourceware.org with SMTP; 11 Oct 2004 17:22:04 -0000 Received: by pippin.tausq.org (Postfix, from userid 1000) id 7F194CD2F8; Mon, 11 Oct 2004 10:22:07 -0700 (PDT) Date: Mon, 11 Oct 2004 18:54:00 -0000 From: Randolph Chung To: gdb@sources.redhat.com Subject: Question about _dl_debug_state and new glibc Message-ID: <20041011172207.GA14151@tausq.org> Reply-To: Randolph Chung Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-GPG: for GPG key, see http://www.tausq.org/gpg.txt User-Agent: Mutt/1.5.5.1+cvs20040105i X-SW-Source: 2004-10/txt/msg00283.txt.bz2 Hi all, I've been away from gdb for a bit, so hopefully this is not something simple I missed while I've been away :) It appears that newer versions of glibc now marks the _dl_debug_state function as hidden, making it not visible to gdb. This breaks the solib tracking code in solib-svr4.c..... Looking at the docs, it looks like the "proper" way for gdb to do this is to look up the r_debug symbol and use the r_brk member to locate _dl_debug_state's address. is there any particular reason why we don't do this in gdb? randolph -- Randolph Chung Debian GNU/Linux Developer, hppa/ia64 ports http://www.tausq.org/