From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <frysk-return-2515-listarch-frysk=sources.redhat.com@sourceware.org>
Received: (qmail 27555 invoked by alias); 15 Nov 2007 18:04:18 -0000
Received: (qmail 27548 invoked by uid 22791); 15 Nov 2007 18:04:17 -0000
X-Spam-Status: No, hits=-2.0 required=5.0 	tests=AWL,BAYES_00,DK_POLICY_SIGNSOME,FORGED_RCVD_HELO,TW_FH
X-Spam-Check-By: sourceware.org
Received: from wildebeest.demon.nl (HELO gnu.wildebeest.org) (83.160.170.119)     by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 15 Nov 2007 18:04:16 +0000
Received: from dijkstra.wildebeest.org ([192.168.1.29]) 	by gnu.wildebeest.org with esmtp (Exim 4.63) 	(envelope-from <mark@klomp.org>) 	id 1Isj4W-0004fY-GB; Thu, 15 Nov 2007 19:04:13 +0100
Subject: Re: fhpd vs RuntimeExceptions
From: Mark Wielaard <mark@klomp.org>
To: Phil Muldoon <pmuldoon@redhat.com>
Cc: frysk@sourceware.org
In-Reply-To: <473C7B74.6090109@redhat.com>
References: <1195050364.3027.24.camel@dijkstra.wildebeest.org> 	 <473C7B74.6090109@redhat.com>
Content-Type: text/plain
Date: Thu, 15 Nov 2007 18:04:00 -0000
Message-Id: <1195149852.3010.33.camel@dijkstra.wildebeest.org>
Mime-Version: 1.0
X-Mailer: Evolution 2.12.1 (2.12.1-3.fc8)
Content-Transfer-Encoding: 7bit
X-Spam-Score: -4.4 (----)
X-IsSubscribed: yes
Mailing-List: contact frysk-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <frysk.sourceware.org>
List-Subscribe: <mailto:frysk-subscribe@sourceware.org>
List-Post: <mailto:frysk@sourceware.org>
List-Help: <mailto:frysk-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: frysk-owner@sourceware.org
X-SW-Source: 2007-q4/txt/msg00136.txt.bz2

Forgot:

On Thu, 2007-11-15 at 17:01 +0000, Phil Muldoon wrote:
> Pending a the full implementation of this it's a pain to see every 
> single exception printed.

Till there is a difference between fatal and user message "exceptions"
you can easily get the old behavior by tweaking CLI.flushMessages():

--- a/frysk-core/frysk/hpd/CLI.java
+++ b/frysk-core/frysk/hpd/CLI.java
@@ -294,7 +294,7 @@ public class CLI {
                 outWriter.print(prefix);
             outWriter.println(tempmsg.getMessage());
            Throwable exc = tempmsg.getException();
-           if (exc != null)
+           if (exc != null && false)
                exc.printStackTrace(outWriter);
             iter.remove();
         }

Or replace false with the heuristic you find acceptable of course.

Cheers,

Mark