From: Roland Schwingel <roland.schwingel@onevision.de>
To: Joel Brobecker <brobecker@adacore.com>, gdb <gdb@sourceware.org>
Subject: Re: Strange stack trace on Windows
Date: Wed, 18 Mar 2009 09:26:00 -0000 [thread overview]
Message-ID: <49C0BE1F.8050909@onevision.de> (raw)
Hi Joel,
Joel Brobecker wrote on 17.03.2009 20:42:56:
> > That sounds interesting... :-)
> > Could you outline that a bit more? Where and how can I do that?
> > (I am digging in gdb's source only for a few days now).
>
> You can try the attached patch. What it does is that it matches
> the "current_pc" with the start address of the associated function
> (if any). If they are identical, then we're at the beginning of
> the function. In that case, we know that the function will appear
> frameless since the frame hasn't been setup, but we also know how to
> unwind properly from it. I can't test the patch right now, so let
> me know how it goes.
First thank you for your patch and time! I really appreciate that!
I adapted your diff (hopefully correctly) to match the i386_frame_cache()
function from gdb's CVS head. Obviously is your i386-tdep.c quite
different to the one from CVS head. I think I did not made any mistake
in adding the comparison.
Unfortunately it does not work.
cache->pc is set from get_frame_func(this_frame).
current_pc is set from get_frame_pc(this_frame)
(BTW: In the current CVS head there is no current_pc anymore
in i386_frame_cache(). I added it on my own.)
In my tests both cache->pc and current_pc are ALWAYS identical.
Mabye it has something to do with your different i386-tdep.c?
Would it help when I create sample code and send it to you?
Again thank you for patch,
Roland
next reply other threads:[~2009-03-18 9:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-18 9:26 Roland Schwingel [this message]
2009-03-19 14:18 ` Joel Brobecker
-- strict thread matches above, loose matches on Subject: below --
2009-03-23 13:12 Roland Schwingel
2009-03-17 15:39 Roland Schwingel
2009-03-17 19:43 ` Joel Brobecker
2009-03-17 15:26 Roland Schwingel
2009-03-17 13:49 Roland Schwingel
2009-03-17 14:27 ` Pedro Alves
2009-03-17 15:08 ` Joel Brobecker
2009-03-17 11:58 Roland Schwingel
2009-03-17 13:19 ` Joel Brobecker
2007-09-29 22:01 Gordon Prieur
2007-09-30 3:00 ` Daniel Jacobowitz
2007-09-30 18:13 ` Eli Zaretskii
2007-10-01 14:03 ` Gordon Prieur
2007-10-01 14:39 ` Joel Brobecker
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=49C0BE1F.8050909@onevision.de \
--to=roland.schwingel@onevision.de \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.org \
/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).