From: Daniel Jacobowitz <drow@false.org>
To: Andrew STUBBS <andrew.stubbs@st.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix segfault on empty else
Date: Fri, 07 Jul 2006 12:39:00 -0000 [thread overview]
Message-ID: <20060707123859.GA20201@nevyn.them.org> (raw)
In-Reply-To: <44AE4063.2080100@st.com>
On Fri, Jul 07, 2006 at 12:07:15PM +0100, Andrew STUBBS wrote:
> Daniel Jacobowitz wrote:
> >Does this work better?
>
> Yes much better, thanks. It now runs all the tests, no matter what, and
> reports crashes as failures. The only exception is the very last one,
> which really is unresolved following the failure of the previous test.
>
> How about the attached patch then?
:REVIEWMAIL:
Yeah, this is OK. Thanks.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-07-07 12:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-20 14:34 Andrew STUBBS
2006-06-20 20:17 ` Daniel Jacobowitz
2006-06-21 10:50 ` Andrew STUBBS
2006-07-06 13:30 ` Daniel Jacobowitz
2006-07-06 16:19 ` Andrew STUBBS
2006-07-06 16:23 ` Daniel Jacobowitz
2006-07-07 11:08 ` Andrew STUBBS
2006-07-07 12:39 ` Daniel Jacobowitz [this message]
2006-07-07 13:36 ` Andrew STUBBS
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=20060707123859.GA20201@nevyn.them.org \
--to=drow@false.org \
--cc=andrew.stubbs@st.com \
--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