Skip to content

No feedback if a command return a non zero exit code #168

Description

@selgueti

A detailed summary of the issue goes here.

When calling an external program, if it does not write anything to stderr and the program returns a non-zero exit code, like a segmentation error, the user is not informed of the error that has just occurred.
Moreover the command appears in green in the console as if everything went well.

What steps will reproduce the problem?

files_to_reproduce.zip

  1. Unzip the archive files_to_reproduce.zip
  2. Open a terminal and verify that the following command produce a segmentation error:
    UnitexToolLogger Fst2List -D files_to_reproduce/DEMA-ASflx.bin -D files_to_reproduce/DEMA-NSflx.bin -a s -d -s ", " -o A-tous-recursive-paths.txt files_to_reproduce/A-tous.fst2

Let's configure the same with the IDE:

  1. Open the menu Info > Preferences...
  2. Select Morphological-mode dictionaries tab
  3. Add the 2 morphological dictionary (.bin file)
  4. Open the graph A-tous.grf
  5. Then open the Explore Graph Path menu (FSGraph > Tools > Explore Graph Paths)
  6. Click on run

What is the expected output?

A message indicating that the operation has failed.
The command should be considere failed in red in the console.

What do you see instead?

No path is printed and the command is considered successful in the console.

More info

The segmentation error occurs with UnitexToolLogger version 3.3.7 and version 4.0alpha

  • Unitex/GramLab IDE version: 4.0.0
  • UnitexToolLogger version: 4.0.0
  • Did this work before?: [ ] yes [x] no

No activity

Activity on this issue will appear here.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions