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

From: Daniel Jacobowitz <drow at false dot org>
To: Rich Coe <Richard dot Coe at med dot ge dot com>
Cc: "H. J. Lu" <hjl at lucon dot org>, gdb at sources dot redhat dot com
Date: Fri, 10 Jun 2005 15:37:21 -0400
Subject: Re: no stack trace with 2.6.11 and gdb 6.3
References: <20050610125855.62ce7313@godzilla> <20050610181140.GA6207@nevyn.them.org> <20050610135940.23bd015c@godzilla> <20050610190531.GA8893@lucon.org> <20050610142058.671c9987@godzilla>

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.

> 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.

-- 
Daniel Jacobowitz
CodeSourcery, LLC

Follow-Ups:
- Re: no stack trace with 2.6.11 and gdb 6.3
  - From: richard . coe

References:
- no stack trace with 2.6.11 and gdb 6.3
  - From: Rich Coe
- Re: no stack trace with 2.6.11 and gdb 6.3
  - From: Daniel Jacobowitz
- Re: no stack trace with 2.6.11 and gdb 6.3
  - From: Rich Coe
- Re: no stack trace with 2.6.11 and gdb 6.3
  - From: H. J. Lu
- Re: no stack trace with 2.6.11 and gdb 6.3
  - From: Rich Coe

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