From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10589 invoked by alias); 11 Jun 2005 00:51:21 -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 10577 invoked by uid 22791); 11 Jun 2005 00:51:16 -0000 Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Sat, 11 Jun 2005 00:51:16 +0000 Received: from drow by nevyn.them.org with local (Exim 4.50) id 1DguDS-0007h8-0U; Fri, 10 Jun 2005 20:51:14 -0400 Date: Sat, 11 Jun 2005 00:51:00 -0000 From: Daniel Jacobowitz To: richard.coe@med.ge.com Cc: "H. J. Lu" , gdb@sources.redhat.com Subject: Re: no stack trace with 2.6.11 and gdb 6.3 Message-ID: <20050611005113.GA29491@nevyn.them.org> Mail-Followup-To: richard.coe@med.ge.com, "H. J. Lu" , gdb@sources.redhat.com References: <20050610193720.GA24094@nevyn.them.org> <200506102115.QAA91634@morpheus> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200506102115.QAA91634@morpheus> User-Agent: Mutt/1.5.8i X-SW-Source: 2005-06/txt/msg00103.txt.bz2 On Fri, Jun 10, 2005 at 04:15:59PM -0500, richard.coe@med.ge.com wrote: > > Daniel Jacobowitz writes: > In a message dated: Fri, 10 Jun 2005 15:37:21 EDT > > On Fri, Jun 10, 2005 at 02:20:58PM -0500, Rich Coe wrote: > > > Yes, after I manually run > > > 'add-symbol-file-from-memory 0xffffe000' > > > I can get a valid traceback. > > > > > > Why doesn't this just work like gdb-6.0 on 2.6.7 ? > > > > Your GDB 6.0 was also patched by Red Hat; again, you would have to ask > > them. > > In this regard, you are shallow. I think every developer has a > certain expectation that when they type backtrace, that the debugger > accurately display the data. I was merely referencing a previously > release where it works, and now it doesn't. > > There is an obvious difference that this is not working. > I'm all for working towards a solution and I don't think you taking pot > shots at Redhat is working toward that end. If you have a beef with > Redhat, I could care less. If you are saying or implying that this is > broken only in a Redhat kernel, then please be less obtuse, because > I'll gladly track this problem down wherever it may lead. Kindly don't be insulting. I'm not "taking a potshot at Red Hat". I know for an absolute fact that GDB 6.0 would not load a vsyscall DSO and automatically backtrace from it. If you have a GDB 6.0- which does, then the patches came from elsewhere, and I can't answer questions about code we don't have. > > > Why does this command run automatically when debugging with gdb from the > > > command line but when attaching to an already running process ? > > > > Because it's different code that detects the new program. > > So it seems that you are well aware of this problem. > Are you recommending that the add-symbol-file-from-memory as the > current solution ? No, I told you that I expected it to work in CVS. If it does not, then someone needs to reproduce your problem using an unpatched GDB and debug it. I do not have a Red Hat x86_64 system on which to reproduce it, but I may be able to elsewhere - if I have time. -- Daniel Jacobowitz CodeSourcery, LLC