public inbox for frysk-bugzilla@sourceware.org help / color / mirror / Atom feed
From: "pmachata at redhat dot com" <sourceware-bugzilla@sourceware.org> To: frysk-bugzilla@sourceware.org Subject: [Bug general/6458] New: Frysk is acting funny around relative paths Date: Fri, 25 Apr 2008 12:17:00 -0000 [thread overview] Message-ID: <20080425121627.6458.pmachata@redhat.com> (raw) 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.
next reply other threads:[~2008-04-25 12:17 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-04-25 12:17 pmachata at redhat dot com [this message] 2008-04-30 18:18 ` [Bug general/6458] " scox at redhat dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20080425121627.6458.pmachata@redhat.com \ --to=sourceware-bugzilla@sourceware.org \ --cc=frysk-bugzilla@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).