clingo-dl terminates with exit code 33 upon bad_alloc exception

[peschue]

clingo-dl returns 33 after showing the error message std::bad_alloc because memory was exhausted and without enumerating any solution. Maybe it should return just 1 (interrupted)?

Related is #18. An exit code of 33 means that all optimal solutions were found and the run was interrupted (see 3. Exit Code Bit Encoding - bits ALLOPT and INT in https://www.mat.unical.it/aspcomp2013/files/aspoutput.txt).

[rkaminsk]

Yes, it should not exit with code 33. I don't think that a combination of ALLOPT and INT ever makes sense. Can you also post the output?

[peschue]

clingo-dl ... files ... --heur=Domain --stats --time=3600 -q1,0 -t4 --fast-exit --outf=2 2>&1

gives the output

... some messages about info: atom does not occur in any rule head: ...

*** ERROR: (clingo-dl): std::bad_alloc
{
  "Solver": "clingo-dl version 1.0.0",
  "Input": [
    ... files as on commandline ...
  ],
  "Call": [
    {

    }
  ],
  "Result": "UNKNOWN",
  "Models": {
    "Number": 0,
    "More": "yes"
  },
  "Calls": 1,
  "Time": {
    "Total": 57.088,
    "Solve": 0.000,
    "Model": 0.000,
    "Unsat": 0.000,
    "CPU": 57.074
  },
  "Threads": 4,
  "Winner": 0,
  "Stats": {
    "Core": {
      "Choices": 0,
      "Conflicts": 0,
      "Backtracks": 0,
      "Backjumps": 0,
      "Restarts": 0,
      "RestartAvg": 0.000,
      "RestartLast": 0
    },
    "More": {
      "CPU": 0.000,
      "Models": 0,
      "Splits": 0,
      "Problems": 0,
      "AvgGPLength": 0.000,
      "Lemma": {
        "Sum": 0,
        "Deleted": 0,
        "Type": [
          {
            "Type": "Short",
            "Sum": 0,
            "Ratio": 0.000,
            "Binary": 0,
            "Ternary": 0
          },
          {
            "Type": "Conflict",
            "Sum": 0,
            "AvgLen": 0.000
          },
          {
            "Type": "Loop",
            "Sum": 0,
            "AvgLen": 0.000
          },
          {
            "Type": "Other",
            "Sum": 0,
            "AvgLen": 0.000
          }
        ]
      }
    },
    "Jumps": {
      "Sum": 0,
      "Max": 0,
      "MaxExec": 0,
      "Avg": 0.000,
      "AvgExec": 0.000,
      "Levels": 0,
      "LevelsExec": 0,
      "Bounded": {
        "Sum": 0,
        "Max": 0,
        "Avg": 0.000,
        "Levels": 0
      }
    },
    "LP": {
      "Rules": {
        "Original": 0,
        "Final": 0
      },
      "Atoms": 0,
      "Bodies": {
        "Original": 0,
        "Final": 0
      },
      "Tight": "yes",
      "Equivalences": {
        "Sum": 0,
        "Atom": 0,
        "Body": 0,
        "Other": 0
      }
    },
    "Problem": {
      "Variables": 0,
      "Eliminated": 0,
      "Frozen": 0,
      "Constraints": {
        "Sum": 0,
        "Binary": 0,
        "Ternary": 0
      },
      "AcycEdges": 0
    }
  }
}

[rkaminsk]

Actually, this is not a bug. Please check potassco/clasp#42 for how to interpret the exit codes. I'll leave the issue in the guide open because we should document this at some point.