This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: how to discover description of error which terminated run
- From: fche at redhat dot com (Frank Ch. Eigler)
- To: John Lumby <johnlumby at hotmail dot com>
- Cc: systemtap maillist <systemtap at sourceware dot org>, <mark at klomp dot org>
- Date: Thu, 06 Dec 2012 18:29:49 -0500
- Subject: Re: how to discover description of error which terminated run
- References: <1354805036.18914.ezmlm@sourceware.org> <COL116-W141FD695CAB035A5D8C81A3450@phx.gbl>
johnlumby wrote:
> [...] What surprises me is that the run continued for a full 0.1
> seconds (over 4000 lines of output) after this message was logged
> before it shut itself down. [...]
The intent is not to lose information unnecessarily; the transport of
that queued information is lightweight enough not to cause overload.
>[...] Makes me wonder? -? is there some way of directing error
> messages such as this to some other channel rather than interspersing
> them into the run output.?? Or else at least making them more distinctive.
I believe errors/warnings already go to stderr as opposed to stdout.
I opened PR14927 to make them even more visible. (Want to give coding
that up a try? We'll help!)
- FChE