From: Tristan Gingold <gingold@adacore.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Florent DEFAY <spira.inhabitant@gmail.com>, gdb@sourceware.org
Subject: Re: scan_prologue/next, misunderstanding
Date: Tue, 19 May 2009 13:39:00 -0000 [thread overview]
Message-ID: <A3723B98-F661-4855-AF34-3B5771B086DC@adacore.com> (raw)
In-Reply-To: <20090519133331.GX17566@adacore.com>
On May 19, 2009, at 3:33 PM, Joel Brobecker wrote:
>> I got inspiration from avr-tdep.c. I still have problems with 'next'.
>> I set a 'printf' in the function skip_prologue and I can tell it is
>> never used.
>
> Just a first guess:
>
> I haven't looked at the code itself, but there are usually more than
> one
> unwinders; for instance, there is a dwarf unwinder that reads the
> frame
> info data from the dwarf data and use that exclusively to do the
> unwinding.
> This might explain why the AVR unwinder based on prologue analysis
> doesn't
> get called.
[ Well the default debug format for avr is stabs... ]
The avr prologue analyzer is somewhat buggy and breaks the next
command. I have a patch to fix that
but didn't yet manage to submit it. Will try next week.
Tristan.
prev parent reply other threads:[~2009-05-19 13:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-19 12:37 Florent DEFAY
2009-05-19 13:33 ` Joel Brobecker
2009-05-19 13:39 ` Tristan Gingold [this message]
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=A3723B98-F661-4855-AF34-3B5771B086DC@adacore.com \
--to=gingold@adacore.com \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--cc=spira.inhabitant@gmail.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