From: Daniel Jacobowitz <dmj+@andrew.cmu.edu>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa] mips heuristic_proc_start fix
Date: Thu, 12 Jul 2001 12:14:00 -0000 [thread overview]
Message-ID: <20010712121358.A25739@nevyn.them.org> (raw)
In-Reply-To: <3B4D4FC6.6090003@cygnus.com>
On Thu, Jul 12, 2001 at 03:20:38AM -0400, Andrew Cagney wrote:
> Hmm, with this patch UINT_MAX would give a fence of VM_MIN_ADDRESS yet
> UINT_MAX-1 would give the above warning.
>
> Could I suggest instead something like:
>
> pc = ADDR_BITS_REMOVE (pc);
> start_pc = pc;
> if (start_pc >= heuristic_fence_post)
> fence = start_pc - heuristic_fence_post;
> else
> fence = 0;
> if (start_pc == 0)
> return 0;
>
> if (heuristic_fence_post == UINT_MAX
> || fence < VM_MIN_ADDRESS)
> fence = VM_MIN_ADDRESS;
>
> The test being moved to before the assignment to make what is happening
> more transparent.
I agree it would be clearer to check for overflow, but just that
won't solve the problem. If start_pc is 2 and instlen is 4, it doesn't
matter what fence gets set to. First time through the for loop we
decrement start_pc by instlen, and that's where the overflow is.
How's this instead? Instead of checking for pc == 0, check for pc <
instlen. If fence overflows, that's fine, because start_pc will be
less than fence; or I could explicitly check for that too.
diff -u -r1.57 mips-tdep.c
--- mips-tdep.c 2001/07/12 17:34:33 1.57
+++ mips-tdep.c 2001/07/12 19:12:20
@@ -1497,19 +1497,19 @@
int seen_adjsp = 0;
pc = ADDR_BITS_REMOVE (pc);
- start_pc = pc;
- fence = start_pc - heuristic_fence_post;
- if (start_pc == 0)
+ instlen = pc_is_mips16 (pc) ? MIPS16_INSTLEN : MIPS_INSTLEN;
+
+ if (pc < instlen)
return 0;
+ start_pc = pc - instlen;
+ fence = start_pc - heuristic_fence_post;
if (heuristic_fence_post == UINT_MAX
|| fence < VM_MIN_ADDRESS)
fence = VM_MIN_ADDRESS;
- instlen = pc_is_mips16 (pc) ? MIPS16_INSTLEN : MIPS_INSTLEN;
-
/* search back for previous return */
- for (start_pc -= instlen;; start_pc -= instlen)
+ for (;; start_pc -= instlen)
if (start_pc < fence)
{
/* It's not clear to me why we reach this point when
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2001-07-12 12:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-06 11:20 Daniel Jacobowitz
2001-07-06 11:27 ` Andrew Cagney
2001-07-06 11:32 ` Daniel Jacobowitz
2001-07-06 11:40 ` Daniel Jacobowitz
2001-07-12 0:47 ` Andrew Cagney
2001-07-12 12:14 ` Daniel Jacobowitz [this message]
2001-07-12 14:11 ` Andrew Cagney
2001-07-12 14:19 ` Daniel Jacobowitz
2001-07-12 14:35 ` 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=20010712121358.A25739@nevyn.them.org \
--to=dmj+@andrew.cmu.edu \
--cc=ac131313@cygnus.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