From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: 63047@debbugs.gnu.org
Cc: dev@jpoiret.xyz, andrew@trop.in
Subject: bug#63047: Can't load glib debug symbols in gdb
Date: Tue, 25 Apr 2023 08:38:44 -0400 [thread overview]
Message-ID: <87edo8qgq3.fsf@gmail.com> (raw)
In-Reply-To: <87ttx5vhoq.fsf@jpoiret.xyz> (Josselin Poiret via Bug reports for's message of "Mon, 24 Apr 2023 09:54:29 +0200")
Hi Andrew,
Josselin Poiret via Bug reports for GNU Guix <bug-guix@gnu.org> writes:
> Hi Andrew,
>
> Andrew Tropin <andrew@trop.in> writes:
>
>> I try to run emacs in gdb with debug symbols for some libs available, I
>> succeed with gtk+, but it doesn't work for glib and glibc. It looks
>> strange to me, but maybe I am doing something wrong.
>>
>> Reproducer:
>>
>> guix shell gdb emacs-next-pgtk glibc:debug gtk+:debug glib:debug \
>> --with-debug-info=glibc --with-debug-info=glib --with-debug-info=gtk+ \
>> --no-grafts -- gdb .emacs-30.0.50-real
>
> At least for glibc, the glibc that is linked against is the one in (gnu
> packages commencement), which is hidden from the user. The one in (gnu
> packages base), which you can refer to with "glibc" is different. You
> can try to find the proper debug output by looking at `guix size` of
> your store path, then finding out the deriver for glibc with `guix gc
> --derivers` and finally looking at the .drv to find out what the debug
> output should be.
>
> For glib, it might be similar, make sure that you're using exactly the
> right store path for it.
Perhaps try on the core-updates branch, where glibc no longer has its
symbols stripped. Another thing that can cause the debug symbols to not
be found is grafts, as described in #48907, so when debugging I'd
recommend using --no-grafts for now.
--
Thanks,
Maxim
next prev parent reply other threads:[~2023-04-25 12:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-24 7:29 bug#63047: Can't load glib debug symbols in gdb Andrew Tropin
2023-04-24 7:54 ` Josselin Poiret via Bug reports for GNU Guix
2023-04-25 12:38 ` Maxim Cournoyer [this message]
2023-09-13 7:54 ` Andrew Tropin
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=87edo8qgq3.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=63047@debbugs.gnu.org \
--cc=andrew@trop.in \
--cc=dev@jpoiret.xyz \
/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).