From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-21828-listarch-gdb=sources.redhat.com@sources.redhat.com>
Received: (qmail 17481 invoked by alias); 13 Jun 2005 15:26:53 -0000
Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:gdb-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/gdb/>
List-Post: <mailto:gdb@sources.redhat.com>
List-Help: <mailto:gdb-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: gdb-owner@sources.redhat.com
Received: (qmail 17447 invoked by uid 22791); 13 Jun 2005 15:26:49 -0000
Received: from rwcrmhc14.comcast.net (HELO rwcrmhc14.comcast.net) (216.148.227.89)
    by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Mon, 13 Jun 2005 15:26:49 +0000
Received: from lucon.org ([24.6.212.230]) by comcast.net (rwcrmhc14) with ESMTP
          id <20050613152647014002cc87e>; Mon, 13 Jun 2005 15:26:47 +0000
Received: by lucon.org (Postfix, from userid 1000)
	id E881764607; Mon, 13 Jun 2005 08:26:46 -0700 (PDT)
Date: Mon, 13 Jun 2005 15:26:00 -0000
From: "H. J. Lu" <hjl@lucon.org>
To: Rich Coe <Richard.Coe@med.ge.com>
Cc: gdb@sources.redhat.com
Subject: Re: no stack trace with 2.6.11 and gdb 6.3
Message-ID: <20050613152646.GB11261@lucon.org>
References: <20050610193720.GA24094@nevyn.them.org> <200506102115.QAA91634@morpheus> <20050611005113.GA29491@nevyn.them.org> <20050611022148.GA14914@lucon.org> <20050613101629.4f54fde1@godzilla>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20050613101629.4f54fde1@godzilla>
User-Agent: Mutt/1.4.1i
X-SW-Source: 2005-06/txt/msg00111.txt.bz2

On Mon, Jun 13, 2005 at 10:16:29AM -0500, Rich Coe wrote:
> On Fri, 10 Jun 2005 19:21:48 -0700
> "H. J. Lu" <hjl@lucon.org> wrote:
> > On Fri, Jun 10, 2005 at 08:51:13PM -0400, Daniel Jacobowitz wrote:
> > > 
> > > 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.
> > 
> > Gdb should support vDSO on Linux 2.6.11/x86_64 with this patch:
> > 
> > http://sources.redhat.com/ml/gdb/2005-06/msg00095.html
> > 
> > If it doesn't work, I will be interested to know.
> > H.J.
> 
> The patch makes it work only if you start the program from the gdb
> command line.  As I said in my original post:

You are saying:

1.

# gdb foo

works.

2. But 

# foo
# gdb foo pid

doesn't work?

Tell me how to reproduce it. I will take a look.


H.J.