From: Kevin Buettner <kevinb@redhat.com>
To: Fabian Cenedese <Cenedese@indel.ch>
Cc: gdb@sources.redhat.com
Subject: Re: View registers from stack frames
Date: Mon, 11 Oct 2004 19:21:00 -0000 [thread overview]
Message-ID: <20041011120241.12f1b9c0@saguaro> (raw)
In-Reply-To: <5.2.0.9.1.20041007090225.01d59d40@NT_SERVER>
On Thu, 07 Oct 2004 09:08:49 +0200
Fabian Cenedese <Cenedese@indel.ch> wrote:
> >> The first two frames seem ok, only frame 3 and more are wrong.
> >> If more info is needed (e.g. the remote debug protocol) I can also
> >> post it here or send to anyone.
> >>
> >> Well, that only leaves me with the cvs version...
> >
> >Give the CVS version a try. If that fails too, could you send me
> >a test case?
>
> The cvs version behaves as 6.2 or 6.2.1. I would love to send you a
> test case but I don't know how to. I'm working with an embedded
> target and some proprietary software. That's why I tried to create
> a memory dump and feed this to gdb so I have something I could
> send to someone else. But that didn't work out.
>
> Would it be helpful to have the debug log of the remote protocol
> communication? Like that you would see what addresses gdb
> probes and the read values. Or maybe a memory dump of the
> call stack of a thread?
Fabian and I communicated privately on this matter. Fabian determined
that it was some custom stack bounds checking code in the prologue which
was causing problems with backtraces. We still haven't figured out
why this bounds checking code didn't cause earlier versions of GDB
problems with its backtraces.
Kevin
next prev parent reply other threads:[~2004-10-11 19:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-05 12:48 Fabian Cenedese
2004-10-05 13:30 ` Andrew Cagney
2004-10-05 14:02 ` Fabian Cenedese
2004-10-05 14:03 ` Daniel Jacobowitz
2004-10-05 15:00 ` Fabian Cenedese
2004-10-05 17:57 ` Fabian Cenedese
2004-10-06 1:57 ` Andrew Cagney
2004-10-06 7:18 ` Fabian Cenedese
2004-10-06 16:41 ` Kevin Buettner
2004-10-07 9:04 ` Fabian Cenedese
2004-10-11 19:21 ` Kevin Buettner [this message]
2004-10-07 17:50 Xinan Tang
[not found] <5.2.0.9.1.20041007134711.01d12d90@NT_SERVER>
[not found] ` <20041007085738.45b5b55a@saguaro>
2004-10-08 10:14 ` Fabian Cenedese
2004-10-11 19:16 ` Kevin Buettner
2004-10-12 14:03 ` Fabian Cenedese
2004-10-16 15:11 ` Kevin Buettner
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=20041011120241.12f1b9c0@saguaro \
--to=kevinb@redhat.com \
--cc=Cenedese@indel.ch \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).