Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@gnu.org>
To: Michael Snyder <msnyder@redhat.com>
Cc: Daniel Jacobowitz <drow@false.org>, cagney <cagney@redhat.com>,
	gdb-patches@sources.redhat.com
Subject: Re: [RFA] Prevent runaway (infinite loop) in mips-tdep.c
Date: Wed, 21 Apr 2004 19:23:00 -0000	[thread overview]
Message-ID: <4086CA37.8070603@gnu.org> (raw)
In-Reply-To: <4086B631.9050304@redhat.com>

>>     (heuristic_proc_start): Warning() already prefixes "Warning: ".

This part is both orthogonal and obvious (the ARI tracks this).

>     * mips-tdep.c (mips_mdebug_frame_cache): Call error to prevent
>     infinite looping by caller.

Lets see what daniel has, but note that bad frames are identified by 
their null frame ID (and the code should not call error).

Andrew



  parent reply	other threads:[~2004-04-21 19:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-21  0:20 Michael Snyder
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 [this message]
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=4086CA37.8070603@gnu.org \
    --to=cagney@gnu.org \
    --cc=cagney@redhat.com \
    --cc=drow@false.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=msnyder@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