Bug 6458 - Frysk is acting funny around relative paths
Summary: Frysk is acting funny around relative paths
Status: RESOLVED DUPLICATE of bug 6465
Alias: None
Product: frysk
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
: P2 normal
Target Milestone: ---
Assignee: Unassigned
Depends on:
Blocks: 5624
  Show dependency treegraph
Reported: 2008-04-25 12:16 UTC by Petr Machata
Modified: 2008-04-30 18:17 UTC (History)
0 users

See Also:
Host: i686-pc-linux-gnu
Target: i686-pc-linux-gnu
Build: i686-pc-linux-gnu
Last reconfirmed:


Note You need to log in before you can comment on or make changes to this bug.
Description Petr Machata 2008-04-25 12:16:27 UTC
Relative paths act suspicious.  The binary that Frysk somehow found in the home
directory is picked.

$ pwd
$ ls ../ke
ls: cannot access ../ke: No such file or directory
$ ./ftrace -- ../ke
7727.7727 attached /home/ant/ke
7727.7727 exited with status 5

This happens even when the path refers to another, valid binary:

$ pwd
$ ls ../ke
$ ../ke
$ ./frysk-core/frysk/bindir/ftrace -- ../ke
7784.7784 attached /home/ant/ke
7784.7784 exited with status 5

It's not just a problem of ftrace:

$ ./frysk-core/frysk/bindir/fstep -- ../ke 2>&1 | grep -v '^\['
Total steps [7915]: 3822

Not sure if bug 5624 sysroot is the right tracker, just a wild guess it might be
Comment 1 Stan Cox 2008-04-30 18:17:56 UTC
Consider relative paths when searching for executable.
* SysRoot.java (findExe): Consider relative paths.

*** This bug has been marked as a duplicate of 6465 ***