Re: no stack trace with 2.6.11 and gdb 6.3

Rich Coe
2005-06-10T19:23:25Z

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 ?
Why does this command run automatically when debugging with gdb from the
command line but when attaching to an already running process ?

R.

On Fri, 10 Jun 2005 12:05:32 -0700
"H. J. Lu" <hjl@lucon.org> wrote:
> On Fri, Jun 10, 2005 at 01:59:40PM -0500, Rich Coe wrote:
> > I downloaded the cvs snapshot gdb-6.3.50.20050607, built, and ran gdb
> > and the problem still persists.
> >
> > What next ?
> >
>
> Try this.
>
> BTW, why does's gdb use
>
> http://www.sourceware.org/bugzilla/
>
> It is very stupid not to.
>
>
> H.J.
> ----
> --- gdb/config/i386/linux64.mt.vdso 2004-11-11 16:47:07.000000000 -0800
> +++ gdb/config/i386/linux64.mt 2005-02-01 13:01:46.056022932 -0800
> @@ -1,5 +1,5 @@
> # Target: GNU/Linux x86-64
> TDEPFILES= amd64-tdep.o amd64-linux-tdep.o \
> i386-tdep.o i387-tdep.o i386-linux-tdep.o glibc-tdep.o \
> - solib.o solib-svr4.o corelow.o
> + solib.o solib-svr4.o corelow.o symfile-mem.o
> DEPRECATED_TM_FILE= solib.h
>

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