Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Michael Chastain <mec.gnu@mindspring.com>
Cc: gdb-patches@sources.redhat.com, eliz@gnu.org
Subject: Re: [rfa/doco] PROBLEMS: remove pr gdb/1505
Date: Sat, 07 Aug 2004 16:24:00 -0000	[thread overview]
Message-ID: <20040807162446.GA3468@nevyn.them.org> (raw)
In-Reply-To: <4114842F.nailOJU11P7U6@mindspring.com>

On Sat, Aug 07, 2004 at 03:26:39AM -0400, Michael Chastain wrote:
> Daniel Jacobowitz <drow@false.org> wrote:
> drow> I'm curious - why do you believe that PR 1505 has been fixed?
> drow> Some particular instance may have been, but the problem definitely
> drow> remains - see discussion on gdb@ this week.
> 
> My test bed says that the problem no longer occurs in the environment
> where it was reported.  Something changed in gdb since the last spin and
> gdb finds the right bottom-of-stack now.
> 
> The problem hasn't occured in any other environments that anyone has
> seen, either.  So I closed the PR.  (I optimized away the feedback step
> because I was the original submitter).  I would tell the original
> submitter: if it happens again, with the same or different platform,
> file a new PR.
> 
> I'm open to alternatives.  How do you suggest we handle PR/1505?

This is what I get for reading the entry in PROBLEMS that you were
removing rather than the PR referenced.

PR 1505 is fixed.  However, the problem of stopping backtraces in
general is not - Andrew made some suggestions.

-- 
Daniel Jacobowitz


  reply	other threads:[~2004-08-07 16:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-07  4:51 Michael Chastain
2004-08-07  5:13 ` Daniel Jacobowitz
2004-08-07  7:26   ` Michael Chastain
2004-08-07 16:24     ` Daniel Jacobowitz [this message]
2004-08-07 17:04       ` Eli Zaretskii
2004-08-07 22:44       ` Michael Chastain

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=20040807162446.GA3468@nevyn.them.org \
    --to=drow@false.org \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=mec.gnu@mindspring.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