public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/15934] Keep directories for argv[0] Date: Tue, 05 Apr 2022 19:06:01 +0000 [thread overview] Message-ID: <bug-15934-4717-da53S8x5At@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-15934-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=15934 --- Comment #2 from Tom Tromey <tromey at sourceware dot org> --- I suppose only the executable would need any special treatment. But for that, I wonder how it would work in the startup-with-shell case. Without a shell, gdb can easily control argv[0]. With a shell, it seems harder, particularly if the executable was specified relative to one working directory, but then the cwd was changed in the gdb session. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2022-04-05 19:06 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-09-05 13:07 [Bug gdb/15934] New: " jan.kratochvil at redhat dot com 2022-04-05 14:38 ` [Bug gdb/15934] " tromey at sourceware dot org 2022-04-05 19:06 ` tromey at sourceware dot org [this message] 2022-04-06 16:00 ` tromey at sourceware dot org 2023-11-13 10:25 ` sam at gentoo dot org 2023-11-13 10:25 ` sam at gentoo dot org
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-15934-4717-da53S8x5At@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).