From: "Jafa" <jafa@silicondust.com>
To: <gdb-patches@sources.redhat.com>
Subject: [patch] missing case in epilogue stub detection
Date: Tue, 26 Aug 2003 22:37:00 -0000 [thread overview]
Message-ID: <00f901c36c22$8fe12250$0502a8c0@scenix.com> (raw)
In-Reply-To: <3F4B9A2A.6020901@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 561 bytes --]
The following patch fixes a bug where an epilogue stub isn't detected and is
erroneously treated as a subroutine.
Fixes step and next errors when at the end of a function for the ip2k. Mips
may have suffered from the same problem but the occurrence of the code would
have been rare.
2003-08-26 Nick Kelsey <nickk@ubicom.com>
* infrun.c (handle_inferior_event): Bug fix in subroutine detection
code regarding dealing with an epilogue stub. The previous code correctly
detected the stub in all cases except where the pc is equal to the stub
entry point.
[-- Attachment #2: infrun.patch --]
[-- Type: application/octet-stream, Size: 255 bytes --]
diff -r1.10 infrun.c
2449,2450c2449
< if (stop_pc == ecs->stop_func_start /* Quick test */
< || (in_prologue (stop_pc, ecs->stop_func_start) &&
---
> if (((stop_pc == ecs->stop_func_start || in_prologue (stop_pc, ecs->stop_func_start)) &&
next prev parent reply other threads:[~2003-08-26 22:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-31 22:01 RFA: patch to display ia64 function pointers J. Johnston
2003-08-25 21:12 ` Kevin Buettner
2003-08-26 17:34 ` J. Johnston
2003-08-26 22:37 ` Jafa [this message]
2003-08-26 22:45 ` [patch] missing case in epilogue stub detection Daniel Jacobowitz
2003-08-26 23:01 ` Jafa
2003-09-07 15:16 ` Daniel Jacobowitz
2003-09-09 3:00 ` Andrew Cagney
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='00f901c36c22$8fe12250$0502a8c0@scenix.com' \
--to=jafa@silicondust.com \
--cc=gdb-patches@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