Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <Michael.Snyder@palmsource.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: GDB Patches ML <gdb-patches@sourceware.org>
Subject: Ping, Re: Infinite backtrace on (eg.) ARM
Date: Thu, 05 Oct 2006 21:51:00 -0000	[thread overview]
Message-ID: <1160084996.9761.93.camel@localhost.localdomain> (raw)
In-Reply-To: <1158951393.22863.87.camel@localhost.localdomain>

On Fri, 2006-09-22 at 11:56 -0700, Michael Snyder wrote:
> On Thu, 2006-09-21 at 22:59 -0400, Daniel Jacobowitz wrote:

> > The second patch had some points of disagreement, but I think Mark and
> > I more or less agreed on the first one before I ran out of time to work
> > on it (I'll be back real soon, hopefully next week, to those), and the
> > third could probably be gotten into acceptable shape readily once the
> > first is in.
> 
> OK, I get it.
> 
> And actually, the 3rd one works pretty well for me by itself
> (with minor tweaking).
> 
> Would you be willing to see it go in that way, just to get 
> something in there to handle the problem?  And put the other
> parts in at your leisure?
> 
> I'll even do it for you.   ;-)

Ping, Daniel?  I was offering to do the work for you, of
isolating and committing the 3rd part of the patch.  This
would stop the infinite backtrace behavior, and would not
be incompatible with what you intend when you get around 
to finishing the work.

Michael


  reply	other threads:[~2006-10-05 21:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-22  1:48 Michael Snyder
2006-09-22  2:59 ` Daniel Jacobowitz
2006-09-22 18:56   ` Michael Snyder
2006-10-05 21:51     ` Michael Snyder [this message]
2006-10-05 22:27       ` Ping, " Daniel Jacobowitz
2006-09-22 19:00 ` Jim Blandy

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=1160084996.9761.93.camel@localhost.localdomain \
    --to=michael.snyder@palmsource.com \
    --cc=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    /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