From: "H. J. Lu" <hjl@lucon.org>
To: Rich Coe <Richard.Coe@med.ge.com>
Cc: Daniel Jacobowitz <drow@false.org>, gdb@sources.redhat.com
Subject: Re: no stack trace with 2.6.11 and gdb 6.3
Date: Fri, 10 Jun 2005 19:05:00 -0000 [thread overview]
Message-ID: <20050610190531.GA8893@lucon.org> (raw)
In-Reply-To: <20050610135940.23bd015c@godzilla>
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
next prev parent reply other threads:[~2005-06-10 19:05 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-10 18:00 Rich Coe
2005-06-10 18:11 ` Daniel Jacobowitz
2005-06-10 19:02 ` Rich Coe
2005-06-10 19:05 ` H. J. Lu [this message]
2005-06-10 19:09 ` Christopher Faylor
2005-06-10 19:10 ` Daniel Jacobowitz
2005-06-10 19:23 ` Rich Coe
2005-06-10 19:37 ` Daniel Jacobowitz
2005-06-10 21:17 ` richard.coe
2005-06-11 0:51 ` Daniel Jacobowitz
2005-06-11 2:21 ` H. J. Lu
2005-06-13 15:19 ` Rich Coe
2005-06-13 15:26 ` H. J. Lu
2005-06-13 15:36 ` Rich Coe
2005-06-13 20:13 ` H. J. Lu
2005-06-13 20:16 ` Daniel Jacobowitz
2005-06-13 20:30 ` H. J. Lu
2005-06-13 20:33 ` Daniel Jacobowitz
2005-06-13 20:36 ` Rich Coe
2005-06-13 20:43 ` Daniel Jacobowitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050610190531.GA8893@lucon.org \
--to=hjl@lucon.org \
--cc=Richard.Coe@med.ge.com \
--cc=drow@false.org \
--cc=gdb@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox