From: Andrew Cagney <cagney@redhat.com>
To: Mark Wielaard <mark@klomp.org>
Cc: Phil Muldoon <pmuldoon@redhat.com>, frysk@sourceware.org
Subject: Re: fhpd vs RuntimeExceptions
Date: Thu, 15 Nov 2007 19:06:00 -0000 [thread overview]
Message-ID: <473C985F.6010103@redhat.com> (raw)
In-Reply-To: <1195149852.3010.33.camel@dijkstra.wildebeest.org>
Mark Wielaard wrote:
> 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():
>
>
That unfortunatly isn't sufficient; the old code in CLI.java was
differentiating between and NPE and other exceptions - dumping the stack
when an NPE occured. I'll restore this behavior; so we're at least back
to a usable status quo (and from a HPD user prospective in a better
position - these back-traces plain suck)
I'll also add a prototype version of CLI.printError() that we discussed;
and have just EvalCommands use it; we can then refine it as needed.
Andrew
> --- 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
>
>
next prev parent reply other threads:[~2007-11-15 19:06 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-14 14:27 Mark Wielaard
2007-11-14 14:45 ` Andrew Cagney
2007-11-14 15:27 ` Kris Van Hees
2007-11-14 15:36 ` Mark Wielaard
2007-11-14 17:33 ` Andrew Cagney
2007-11-14 19:11 ` Mark Wielaard
2007-11-15 17:01 ` Phil Muldoon
2007-11-15 17:42 ` Mark Wielaard
2007-11-15 18:19 ` Phil Muldoon
2007-11-15 18:25 ` Sami Wagiaalla
2007-11-16 11:21 ` Mark Wielaard
2007-11-15 18:21 ` Sami Wagiaalla
2007-11-15 20:33 ` Kris Van Hees
2007-11-16 10:12 ` Mark Wielaard
2007-11-15 18:46 ` Andrew Cagney
2007-11-16 10:15 ` Mark Wielaard
2007-11-15 20:41 ` Kris Van Hees
2007-11-15 22:11 ` Phil Muldoon
2007-11-15 23:09 ` Kris Van Hees
2007-11-16 10:42 ` Mark Wielaard
2007-11-15 18:04 ` Mark Wielaard
2007-11-15 18:22 ` Phil Muldoon
2007-11-15 19:06 ` Andrew Cagney [this message]
2007-11-16 10:28 ` Mark Wielaard
2007-11-16 14:32 ` Andrew Cagney
2007-11-26 10:18 ` Mark Wielaard
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=473C985F.6010103@redhat.com \
--to=cagney@redhat.com \
--cc=frysk@sourceware.org \
--cc=mark@klomp.org \
--cc=pmuldoon@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).