Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@redhat.com>
To: cagney <cagney@redhat.com>, gdb-patches@sources.redhat.com
Subject: [RFA] Prevent runaway (infinite loop) in mips-tdep.c
Date: Wed, 21 Apr 2004 00:20:00 -0000	[thread overview]
Message-ID: <4085BE65.3000402@redhat.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 141 bytes --]

Hi Andrew,

This change will prevent the caller(s) of mips_mdebug_frame_id from
infinite-looping when we get badly lost on the stack frame.


[-- Attachment #2: mips --]
[-- Type: text/plain, Size: 1757 bytes --]

2004-04-21  Michael Snyder  <msnyder@redhat.com>

	* mips-tdep.c (mips_mdebug_frame_cache): Call error to prevent
	infinite looping by caller.
	(heuristic_proc_start): Warning() already prefixes "Warning: ".

Index: mips-tdep.c
===================================================================
RCS file: /cvs/src/src/gdb/mips-tdep.c,v
retrieving revision 1.287
diff -p -r1.287 mips-tdep.c
*** mips-tdep.c	29 Mar 2004 17:58:05 -0000	1.287
--- mips-tdep.c	21 Apr 2004 00:15:54 -0000
*************** mips_mdebug_frame_cache (struct frame_in
*** 1508,1514 ****
      /* I'm not sure how/whether this can happen.  Normally when we
         can't find a proc_desc, we "synthesize" one using
         heuristic_proc_desc and set the saved_regs right away.  */
!     return cache;
  
    /* Extract the frame's base.  */
    cache->base = (frame_unwind_register_signed (next_frame, NUM_REGS + PROC_FRAME_REG (proc_desc))
--- 1508,1514 ----
      /* I'm not sure how/whether this can happen.  Normally when we
         can't find a proc_desc, we "synthesize" one using
         heuristic_proc_desc and set the saved_regs right away.  */
!     error ("Can't find frame info.");
  
    /* Extract the frame's base.  */
    cache->base = (frame_unwind_register_signed (next_frame, NUM_REGS + PROC_FRAME_REG (proc_desc))
*************** heuristic_proc_start (CORE_ADDR pc)
*** 1887,1893 ****
  	    static int blurb_printed = 0;
  
  	    warning
! 	      ("Warning: GDB can't find the start of the function at 0x%s.",
  	       paddr_nz (pc));
  
  	    if (!blurb_printed)
--- 1887,1893 ----
  	    static int blurb_printed = 0;
  
  	    warning
! 	      ("GDB can't find the start of the function at 0x%s.",
  	       paddr_nz (pc));
  
  	    if (!blurb_printed)

             reply	other threads:[~2004-04-21  0:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-21  0:20 Michael Snyder [this message]
2004-04-21  0:53 ` Daniel Jacobowitz
2004-04-21 17:58   ` Michael Snyder
2004-04-21 19:18     ` Daniel Jacobowitz
2004-04-21 19:23     ` Andrew Cagney
2004-04-22 21:11       ` Michael Snyder

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=4085BE65.3000402@redhat.com \
    --to=msnyder@redhat.com \
    --cc=cagney@redhat.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