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.
--
Summary: Frysk is acting funny around relative paths
Product: frysk
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: general
AssignedTo: frysk-bugzilla at sourceware dot org
ReportedBy: pmachata at redhat dot com
GCC build triplet: i686-pc-linux-gnu
GCC host triplet: i686-pc-linux-gnu
GCC target triplet: i686-pc-linux-gnu
OtherBugsDependingO 5624
nThis:
http://sourceware.org/bugzilla/show_bug.cgi?id=6458
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.