From: David Daney <ddaney@avtrex.com>
To: gdb@sources.redhat.com
Subject: Unable to step over (n and ni) on mipsel-linux...
Date: Fri, 20 Aug 2004 19:02:00 -0000 [thread overview]
Message-ID: <412649F4.9040002@avtrex.com> (raw)
GNU gdb 6.2_2004-08-19-cvs
from the gdb_6_2-branch yesterday.
../gdbcvs/src/configure --build=i686-pc-linux --host=mipsel-linux
--target=mipsel-linux --enable-tui=no
Most of the time when I do next or nexti, gdb is treating it as if I did
step or stepi.
I have tracked the problem down to this portion of code:
infrun.c: 2322
.
.
.
if (frame_id_eq (frame_unwind_id (get_current_frame ()),
step_frame_id))
{
/* It's a subroutine call. */
CORE_ADDR real_stop_pc;
.
.
.
When there is a subroutine call this if statement fails. It never
thinks "It's a subroutine call."
Something is horked up in the frame code, but I cannot figure out where.
David Daney.
next reply other threads:[~2004-08-20 19:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-20 19:02 David Daney [this message]
2004-08-20 19:20 ` Theodore A. Roth
2004-08-23 17:14 ` Andrew Cagney
2004-08-23 18:04 ` David Daney
2004-08-23 18:26 ` Andrew Cagney
2004-08-23 18:42 ` David Daney
2004-08-23 18:48 ` Daniel Jacobowitz
2004-08-23 19:01 ` David Daney
2004-08-23 19:22 ` Daniel Jacobowitz
2004-08-24 19:29 ` Andrew Cagney
2004-08-23 19:05 ` Michael Chastain
2004-08-23 19:19 ` David Daney
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=412649F4.9040002@avtrex.com \
--to=ddaney@avtrex.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