public inbox for insight-prs@sourceware.org help / color / mirror / Atom feed
From: ama@mit.edu To: insight-gnats@sources.redhat.com Subject: insight/275: proc initialize_paths: relative symlinks incorrectly resolved Date: Fri, 30 Sep 2005 04:04:00 -0000 [thread overview] Message-ID: <20050930035447.25297.qmail@sourceware.org> (raw) >Number: 275 >Category: insight >Synopsis: proc initialize_paths: relative symlinks incorrectly resolved >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Fri Sep 30 04:03:01 UTC 2005 >Closed-Date: >Last-Modified: >Originator: ama@mit.edu >Release: 6.30.50.20050919 >Organization: >Environment: >Description: the embedded tcl procedure initialize_paths in libgui/src/paths.c incorrectly resolves relative symlinks. $ insight ide_initialize_paths failed: couldn't change working directory to "/home/ama/../encap/insight-6.30.50.20050919/bin": no such file or directory >How-To-Repeat: let insight be a relative symbolic link on your path $ insight >Fix: patch attached >Release-Note: >Audit-Trail: >Unformatted: ----gnatsweb-attachment---- Content-Type: text/x-patch; name="patch.diff" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="patch.diff" LS0tIHNyYy9saWJndWkvc3JjL3BhdGhzLmMub3JpZwkyMDAyLTAyLTA1IDE4OjE2OjE2LjAwMDAw MDAwMCAtMDUwMAorKysgc3JjL2xpYmd1aS9zcmMvcGF0aHMuYwkyMDA1LTA5LTI5IDIzOjQyOjMy LjAwMDAwMDAwMCAtMDQwMApAQCAtNjAsMTMgKzYwLDE1IEBACiAgIH1cblwKICAgc2V0IGhlcmUg W3B3ZF1cblwKICAgc2V0IGV4ZWNfbmFtZSBbaW5mbyBuYW1lb2ZleGVjdXRhYmxlXVxuXAorICBz ZXQgdGhlcmUgW2ZpbGUgZGlybmFtZSAkZXhlY19uYW1lXVxuXAogICBpZiB7W3N0cmluZyBjb21w YXJlIFtmaWxlIHR5cGUgJGV4ZWNfbmFtZV0gXCJsaW5rXCJdID09IDB9IHtcblwKICAgICBzZXQg ZXhlY19uYW1lIFtmaWxlIHJlYWRsaW5rICRleGVjX25hbWVdXG5cCiAgICAgaWYge1tzdHJpbmcg Y29tcGFyZSBbZmlsZSBwYXRodHlwZSAkZXhlY19uYW1lXSBcInJlbGF0aXZlXCJdID09IDB9IHtc blwKLSAgICAgICAgc2V0IGV4ZWNfbmFtZSBbZmlsZSBqb2luIFtwd2RdICRleGVjX25hbWVdXG5c CisgICAgICAgIHNldCBleGVjX25hbWUgW2ZpbGUgam9pbiAkdGhlcmUgJGV4ZWNfbmFtZV1cblwK ICAgICB9XG5cCisgICAgc2V0IHRoZXJlIFtmaWxlIGRpcm5hbWUgJGV4ZWNfbmFtZV1cblwKICAg fVxuXAotICBjZCBbZmlsZSBkaXJuYW1lICRleGVjX25hbWVdXG5cCisgIGNkICR0aGVyZVxuXAog ICAjIEhhbmRsZSBidWlsZCB3aXRoIC0tZXhlYy1wcmVmaXggYW5kIGJ1aWxkIHdpdGhvdXQuXG5c CiAgIHNldCBkIFtmaWxlIGpvaW4gW2ZpbGUgZGlybmFtZSBbcHdkXV0gdXNyIHNoYXJlXVxuXAog ICBsYXBwZW5kIHByZWZkaXJzICRkXG5cCg==
reply other threads:[~2005-09-30 4:04 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20050930035447.25297.qmail@sourceware.org \ --to=ama@mit.edu \ --cc=insight-gnats@sources.redhat.com \ /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).