Re: no stack trace with 2.6.11 and gdb 6.3

Rich Coe
2005-06-13T15:19:13Z

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:
> After reviewing the patch made to bug#146087, I found that I can get
> a valid traceback if I issue the following request:
>
> add-symbol-file-from-memory 0xffffe000
> The interesting part is that this also failing on x86 systems, not just
> x86_64.
>
> If you start an application from within gdb on the command line,
> the following line is printed out:
> Loaded system supplied DSO at 0xffffe000

--
Rich Coe richard.coe@med.ge.com
General Electric Healthcare Technologies
Global Software Platforms, Computer Technology Team