From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24050 invoked by alias); 25 Oct 2003 00:09:56 -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 24043 invoked from network); 25 Oct 2003 00:09:55 -0000 Received: from unknown (HELO lionfish.az05.bull.com) (141.112.4.90) by sources.redhat.com with SMTP; 25 Oct 2003 00:09:55 -0000 Received: from us-phx1.az05.bull.com (us-phx1.az05.bull.com [141.112.40.1]) by lionfish.az05.bull.com (8.12.10/8.12.10) with ESMTP id h9P09Q9h031082; Fri, 24 Oct 2003 17:09:26 -0700 Subject: Re: gdb6.0 and statically linked threaded programs To: Daniel Jacobowitz Cc: gdb@sources.redhat.com Message-ID: From: Todd.Kneisel@Bull.com Date: Sat, 25 Oct 2003 00:09:00 -0000 MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii X-SW-Source: 2003-10/txt/msg00282.txt.bz2 > On Thu, Oct 23, 2003 at 01:33:55PM -0700, Todd.Kneisel@Bull.com wrote: > > I just tried gdbserver and it's broken worse than native gdb. For both > > statically and dynamically linked threaded programs, gdbserver fails > > the same way that native gdb does for statically linked programs. > > Then you have gdbserver set up wrong or are using an older version - > I've tested it recently. You'll have to investigate more. > > -- > Daniel Jacobowitz > MontaVista Software Debian GNU/Linux Developer I've found that gdbserver is failing because we're on an ia64 system. The configure.srv file uses the default srv_linux_thread_db=no for ia64 systems, which disables the code that initializes the thread layer. I changed srv_linux_thread_db to yes and reconfigured and now the thread layer is initialized, but breakpoints are not implemented for the ia64 in gdbserver. We're evaluating our options now. We may go back to gdb 5 and live without the stack traces that were fixed for ia64 in gdb 6. Thanks for your help, Todd Kneisel.