public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "palves at redhat dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/15979] current_directory not updated if chdir done from python Date: Tue, 01 Oct 2013 15:47:00 -0000 [thread overview] Message-ID: <bug-15979-4717-WIOrCf0STr@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-15979-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=15979 Pedro Alves <palves at redhat dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |palves at redhat dot com --- Comment #2 from Pedro Alves <palves at redhat dot com> --- > 1) it doesn't handle symlinks (whether it should or not is debatable, so this > could be a non-bug, depending on how wants to define things). IMO, "cd" should follow continue not resolving symlinks by default, like sh and bash. See <http://pubs.opengroup.org/onlinepubs/009695399/utilities/cd.html>: > The following options shall be supported by the implementation: > > -L > Handle the operand dot-dot logically; symbolic link components shall not > be resolved before dot-dot components are processed (see steps 8. and 9. in > the DESCRIPTION). > -P > Handle the operand dot-dot physically; symbolic link components shall be > resolved before dot-dot components are processed (see step 7. in the > DESCRIPTION). If people want gdb's "cd" to resolve symlinks, we could add -P/-L for that. -- You are receiving this mail because: You are on the CC list for the bug.
prev parent reply other threads:[~2013-10-01 15:47 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-09-25 23:33 [Bug gdb/15979] New: " dje at google dot com 2013-09-25 23:53 ` [Bug gdb/15979] " dje at google dot com 2013-10-01 15:47 ` palves at redhat dot com [this message]
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=bug-15979-4717-WIOrCf0STr@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@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).