From: "Ludovic Courtès" <ludo@gnu.org>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: 61486@debbugs.gnu.org
Subject: [bug#61486] [PATCH] system: Update skeleton gdbinit.
Date: Mon, 27 Feb 2023 23:34:39 +0100 [thread overview]
Message-ID: <87o7peg2kg.fsf@gnu.org> (raw)
In-Reply-To: <08c09168cea2ab383bb6664682d3e8c52f70f131.1676314760.git.efraim@flashner.co.il> (Efraim Flashner's message of "Mon, 13 Feb 2023 21:00:22 +0200")
Hi Efraim,
Efraim Flashner <efraim@flashner.co.il> skribis:
> * gnu/system/shadow.scm (default-skeleton): Update gdbinit to also
> search for debug packages in guix-home.
> (skeleton-directory): Move .gdbinit to .config/gdb/gdbinit.
[...]
> (use-modules (gdb))
> (execute (string-append \"set debug-file-directory \"
> (or (getenv \"GDB_DEBUG_FILE_DIRECTORY\")
> - \"~/.guix-profile/lib/debug\")))
> + \"~/.guix-profile/lib/debug\"
> + \"~/.guix-home/profile/lib/debug\")))
This won’t have the desired effect:
--8<---------------cut here---------------start------------->8---
scheme@(guile-user)> (or #f "a" "b")
$10 = "a"
--8<---------------cut here---------------end--------------->8---
Perhaps we should check with ‘file-exists?’ which one to pick, probably
giving higher precedence to ~/.guix-home/profile since Guix Home users
might have both (I do).
> + (when (file-exists? ".gdbinit")
> + (mkdir-p ".config/gdb")
> + (rename-file ".gdbinit" ".config/gdb/gdbinit"))
I couldn’t believe it so I had to check the manual and yes, GDB does
look for ~/.config/gdb/gdbinit! Incredible.
Thanks,
Ludo’.
next prev parent reply other threads:[~2023-02-27 22:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-13 19:00 [bug#61486] [PATCH] system: Update skeleton gdbinit Efraim Flashner
2023-02-27 22:34 ` Ludovic Courtès [this message]
2023-02-28 7:53 ` Efraim Flashner
2023-03-03 10:46 ` Ludovic Courtès
2023-03-01 6:43 ` Efraim Flashner
2023-03-03 10:46 ` Ludovic Courtès
2023-03-07 14:35 ` bug#61486: " Efraim Flashner
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87o7peg2kg.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=61486@debbugs.gnu.org \
--cc=efraim@flashner.co.il \
/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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).