Relative paths act suspicious. The binary that Frysk somehow found in the home directory is picked. $ pwd /home/ant/frysk-git-2/build/frysk-core/frysk/bindir $ ls ../ke ls: cannot access ../ke: No such file or directory $ ./ftrace -- ../ke 7727.7727 attached /home/ant/ke joha 7727.7727 exited with status 5 This happens even when the path refers to another, valid binary: $ pwd /home/ant/frysk-git-2/build $ ls ../ke ../ke $ ../ke ahoj $ ./frysk-core/frysk/bindir/ftrace -- ../ke 7784.7784 attached /home/ant/ke joha 7784.7784 exited with status 5 It's not just a problem of ftrace: $ ./frysk-core/frysk/bindir/fstep -- ../ke 2>&1 | grep -v '^\[' joha Total steps [7915]: 3822 Not sure if bug 5624 sysroot is the right tracker, just a wild guess it might be related.
Consider relative paths when searching for executable. * SysRoot.java (findExe): Consider relative paths. *** This bug has been marked as a duplicate of 6465 ***