GDB ManipulatorExitCodes

GDB-Manipulator exit codes Exit 0

returned because all test-results are read/executed correctly Exit -1

Exit -2

Error while analysing gdb-client:Output stream Exit -3

Error while handling gdb-server Exit -4

Error with the file or directory Exit -5

missing at least one required argument Exit -6

failed to create Windows processes Exit -7

Error while handling gdb-client Exit -8

failed to send a command via GDB. Check connection or communication. Check if the GDB-Server is running(on the same port) Exit -9

Error with the file or directory. possible reason is a wrong/not existing elf file Exit -10

Failed in test execution. Possible reason might be a target reset. Exit -11

The target has send the command to terminate the gdb connection Exit -12

Failed to evaluate the Target_Mode. It is possible that the mode has been opt out by the compiler. This is a linker bug!

Please check https://gcc.gnu.org/bugzilla/show_bug.cgi?id=43038\ To bypass this bug it is possible to use this variable:

  extern volatile const uint8_t EUNIT_TARGET_MODE;"
  volatile uint8_t EUNIT_TARGET_MODE_LTO = EUNIT_TARGET_MODE;

It also could be possible the functions: "detachTarget" and "printOverGdb" as been opt out.

Its suffice to refer the functions in volatile pointers or to disable the LTO. Exit -13

Error while analysing gdb-client:Error stream Exit with SIGINT | SIGABRT | SIGTERM

those signals are catched and result an cleanup (kill all child processes)