This is the mail archive of the gdb@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: no stack trace with 2.6.11 and gdb 6.3


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.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]