From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22827 invoked by alias); 13 Jun 2005 20:43:12 -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 22802 invoked by uid 22791); 13 Jun 2005 20:43:08 -0000 Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Mon, 13 Jun 2005 20:43:07 +0000 Received: from drow by nevyn.them.org with local (Exim 4.50) id 1Dhvlx-0006r7-Fs; Mon, 13 Jun 2005 16:43:05 -0400 Date: Mon, 13 Jun 2005 20:43:00 -0000 From: Daniel Jacobowitz To: Rich Coe Cc: "H. J. Lu" , gdb@sources.redhat.com Subject: Re: no stack trace with 2.6.11 and gdb 6.3 Message-ID: <20050613204305.GA26104@nevyn.them.org> Mail-Followup-To: Rich Coe , "H. J. Lu" , gdb@sources.redhat.com References: <20050610193720.GA24094@nevyn.them.org> <200506102115.QAA91634@morpheus> <20050611005113.GA29491@nevyn.them.org> <20050611022148.GA14914@lucon.org> <20050613101629.4f54fde1@godzilla> <20050613152646.GB11261@lucon.org> <20050613153427.76813847@godzilla> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050613153427.76813847@godzilla> User-Agent: Mutt/1.5.8i X-SW-Source: 2005-06/txt/msg00123.txt.bz2 On Mon, Jun 13, 2005 at 03:34:27PM -0500, Rich Coe wrote: > I found out what I was not seeing on Friday. > The original use case used 'gdb -p PID', and it still did not work. > I've found this message from gdb though: > warning: Could not load vsyscall page because no executable was specified > > If I invoke it gdb with 'gdb gtest PID', then the current gdb cvs version > works as expected. > > Is /proc/PID/exe linux specific ? > > I need to look at the -p invocation. > > BTW, the cvs version is missing this patch: > --- gdb/config/i386/linux64.mt.vdso 2004-11-11 16:47:07.000000000 -0800 > +++ gdb/config/i386/linux64.mt 2005-02-01 13:01:46.056022932 -0800 > @@ -1,5 +1,5 @@ > # Target: GNU/Linux x86-64 > TDEPFILES= amd64-tdep.o amd64-linux-tdep.o \ > i386-tdep.o i387-tdep.o i386-linux-tdep.o glibc-tdep.o \ > - solib.o solib-svr4.o corelow.o > + solib.o solib-svr4.o corelow.o symfile-mem.o > DEPRECATED_TM_FILE= solib.h > OK, now we're talking. That warning says, on the following line, "please use the file command first"; so I'm glad to hear that 'gdb gtest PID' works OK. The problem arises because we load /proc/PID/exe after we check for the vsyscall DSO. They're in very different places, so it'll take a little prodding to get them to happen in the right order. One way would be to move the inferior-created observer later, but I'm not sure if the other users of this observer should happen early or late. -- Daniel Jacobowitz CodeSourcery, LLC