View Issue Details

IDProjectCategoryView StatusLast Update
0002934Slicer4Core: Base Codepublic2018-03-31 00:37
ReporterfedorovAssigned Tojcfr 
PriorityhighSeverityminorReproducibilityalways
Status assignedResolutionopen 
Product Version 
Target VersionSlicer 4.11.0Fixed in Version 
Summary0002934: Console output logging for Windows
Description

see http://massmail.spl.harvard.edu/public-archives/slicer-devel/2013/011264.html

from Francois Budin:

Hi JC,

I think even just a log file would be very helpful to know if and what went wrong. Otherwise, being able to just open a new terminal with the environment set up would be great too.
I tried to run "Slicer --cmd" since you mentioned that such an option already exists but I didn't get anything (apart from opening a new instance of Slicer).
Thanks,

Francois

from Andriy Fedorov:

JC,

I agree with Francois. I am perfectly fine with inconsistent behavior
across platforms (meaning, no console output on Windows), as long as
there is some way to get that output log. IMO, a log file of some sort
would be more helpful than a dialog box.

AF

Additional Information

From 0002475: It is not possible to get CLI parameters description, because "--help" has no effect.

TagsNo tags attached.

Relationships

has duplicate 0002475 closedjcfr Running CLIs from command line on Windows console produces no console output 
has duplicate 0002691 closedjcfr No output messages in the slicer command 
has duplicate 0001683 closedjcfr ctk app launcher doesn't handle windows command console 
related to 0003408 closedjcfr Launcher and command line output broken on Windows 
child of 0002376 closedjcfr Inconsistent behavior of Slicer launcher command options output across systems 

Activities

fedorov

fedorov

2013-02-14 08:35

developer   ~0007928

It would also be great if somehow the resolution of this issue fixed the fact that dashboard tests failing on Windows do not have any console output. These failing tests are rather useless, because they do not help in localizing the problem. Few of the many examples:

http://trunk.cdash.org/testDetails.php?test=3072116&build=64664
http://trunk.cdash.org/testDetails.php?test=3429598&build=64448

fedorov

fedorov

2015-03-28 12:12

developer   ~0012990

see http://slicer-devel.65872.n3.nabble.com/VTK-errors-and-warnings-in-CXX-tests-td4033751.html

lassoan

lassoan

2015-03-29 08:04

developer   ~0012991

For showing the console output on the dashboard on Windows, probably the simplest would be:

  • always build Slicer as a console application
  • put the console-enabled launcher in the build tree
  • put the non-console-enabled launcher into the install tree
pieper

pieper

2015-03-29 09:17

administrator   ~0012992

I would not want the releases built with console on unless there is a way to suppress the black dos box popping up (I haven't looked in a while, but last time I checked that was the only way to get console output).

On the other hand when building in debug mode, or when testing is enabled, it would be fine for the dos box to pop up.

lassoan

lassoan

2015-03-29 09:53

developer   ~0012993

If you start any process (either console or window based) with QProcess, the new process will not have a console.

So, if you launch SlicerApp-real.exe with a window based launcher (CTKAppLauncherW.exe) then there will be no black boxes. If you run the same SlicerApp-real.exe with a console based launcher (CTKAppLauncher.exe) then it will have a console and Slicer outputs will be redirected to that.

Issue History

Date Modified Username Field Change
2013-02-11 09:14 fedorov New Issue
2013-02-11 09:14 fedorov Status new => assigned
2013-02-11 09:14 fedorov Assigned To => pieper
2013-02-11 09:15 fedorov Relationship added child of 0002376
2013-02-11 09:17 jcfr Assigned To pieper => jcfr
2013-02-11 09:17 jcfr Priority normal => high
2013-02-11 09:17 jcfr Target Version => Slicer 4.3.0
2013-02-14 08:35 fedorov Note Added: 0007928
2013-09-03 10:38 jcfr Relationship added has duplicate 0002475
2013-09-03 10:39 jcfr Additional Information Updated
2013-09-03 10:39 jcfr Relationship added related to 0002691
2013-09-03 10:40 jcfr Target Version Slicer 4.3.0 => Slicer 4.3.1
2013-09-19 13:33 jcfr Relationship added related to 0003408
2013-10-01 11:50 jcfr Target Version Slicer 4.3.1 => Slicer 4.3.2
2014-03-06 10:15 nicole Target Version Slicer 4.3.2 => Slicer 4.4.0
2014-03-07 11:15 jcfr Priority high => normal
2014-03-07 11:15 jcfr Priority normal => high
2014-03-07 11:15 jcfr Severity major => minor
2014-05-13 08:29 jcfr Relationship replaced has duplicate 0002691
2014-05-13 08:30 jcfr Relationship added has duplicate 0001683
2014-11-02 03:31 jcfr Target Version Slicer 4.4.0 => Slicer 4.4.1
2015-03-28 12:12 fedorov Note Added: 0012990
2015-03-29 08:04 lassoan Note Added: 0012991
2015-03-29 09:17 pieper Note Added: 0012992
2015-03-29 09:53 lassoan Note Added: 0012993
2015-09-01 10:29 jcfr Target Version Slicer 4.4.1 => Slicer 4.5.0-1
2015-10-27 10:33 jcfr Target Version Slicer 4.5.0-1 => Slicer 4.5.1
2016-10-12 02:56 jcfr Target Version Slicer 4.5.1 => Slicer 4.7.0
2017-09-26 10:55 jcfr Target Version Slicer 4.7.0 => Slicer 4.9.0
2018-03-31 00:37 jcfr Target Version Slicer 4.9.0 => Slicer 4.11.0