This is the mail archive of the systemtap@sourceware.org mailing list for the systemtap project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: how to discover description of error which terminated run

Hi -

> >>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!)
> 
> I read the Bug Report.    Looks interesting.    I can certainly try.
> Just point me to where the error messages are written.

In the context of staprun/stapio (pass-5 error messages coming from
the running script), they are pretty localised.  

One way would be to change SRC/staprun/common.c function eprintf().
Around we could emit a \033[31m ... \033[m wrapper around the vfprintf(stderr),
but conditional on isatty(stdout-filehandle), and/or a runtime configuration
item such as a SYSTEMTAP_NOCOLOR environment variable.

- FChE
Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]