From: "Nick Kelsey" <nickkelsey@silicondust.com>
To: <gdb@sources.redhat.com>
Subject: Frame context problem
Date: Thu, 03 Jul 2003 20:36:00 -0000 [thread overview]
Message-ID: <009101c341a2$81adbc20$0a02a8c0@scenix.com> (raw)
Hi guys,
So close... so close :-)
Situation: At the end of a function, click step-over or step-into...
- single steps until it reaches the epilogue stub.
- asks for the frame, I return the FP as it was for the function, and the PC
return address to get back to the caller.
- gdb inserts a breakpoint at the return address I specified.
- gdb runs and stops at the breakpoint correctly.
- gdb removes the breakpoint, single steps, re-inserts the breakpoint and
continues!!!
So it must think that the context is wrong... can you please point me in the
right direction? Where is the decision made regarding deciding if this was
were it was ment to stop?
Thnaks
Nick
next reply other threads:[~2003-07-03 20:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-03 20:36 Nick Kelsey [this message]
2003-07-04 3:50 Jafa
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='009101c341a2$81adbc20$0a02a8c0@scenix.com' \
--to=nickkelsey@silicondust.com \
--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).