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: Mon, 23 Mar 2009 13:12:00 -0000 [thread overview]
Message-ID: <49C78A88.5010908@onevision.de> (raw)
Hi Joel...
Thanks for your reply...
gdb-owner@sourceware.org wrote on 19.03.2009 15:18:06:
> [...]
> The idea is that, during a function call made during single-stepping,
> you'll stop at the first instruction of the function. At this point,
> we want to use the standard method of computing the frame cache rather
> than using the alternative method of trusting the %ebp register.
> This is what the check that I added was about.
>
> The patch that I sent was to be made on top of the first patch
> that I sent long ago. Did you do that?
Sure. I made my changes on top of your older patch. I studied your old/new
patch over and over. I had to slightly adjust it as your new patch does not
100% match the current cvs code. If you like I send you my full i386-tdep.c
(it is quite fat - so I do not attach it now)
>
> > In my tests both cache->pc and current_pc are ALWAYS identical.
>
> They should be identical when you step into a function during
> your "next" operation, but other should be different. If this is not
> the case, then I missed something (maybe something obvious).
Would it help if I make a simple plain c example (source + executable code)
which you can step thru on your own? If you have the time to do so...
Roland
next reply other threads:[~2009-03-23 13:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-23 13:12 Roland Schwingel [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-03-18 9:26 Roland Schwingel
2009-03-19 14:18 ` Joel Brobecker
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=49C78A88.5010908@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).