Opened 10 months ago

Closed 10 months ago

Last modified 9 months ago

#20 closed defect (invalid)

Use error output for actual errors only

Reported by: tkratochvila Owned by: mornfall
Priority: minor Milestone: 5.0
Component: UI Keywords: STDERR
Cc:

Description

When there is no error, print the output to STDOUT instead of STDERR.
For example, in divine version 4.1.6+43d9a505081f, command divine verify MuxDemux?.c will output the following lines to STDERR:
compiling MuxDemux?.c
a report was written to MuxDemux?.report

Change History (2)

comment:1 Changed 10 months ago by mornfall

Resolution: invalid
Status: newclosed

This is not how stdout/stderr works. In divine, like in many other tools, informational (progress) output goes to stderr, the actual output of the command goes to stdout. In case of divine, a short version of the machine-parseable verification report goes to stdout. Try something like this: curl http://example.com > output.html -- you wouldn't want the progress bar to end up in the html either.

comment:2 Changed 9 months ago by mornfall

Milestone: future5.0

Milestone renamed

Note: See TracTickets for help on using tickets.