From: Yannick Koehler <yannick.koehler@colubris.com>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] Feature Request: compiling debug + symbol install ebuild?
Date: Tue, 5 Nov 2002 04:49:12 -0500 [thread overview]
Message-ID: <200211050449.14076.yannick.koehler@colubris.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
Recently I hitted a problem with valgrind which required me to re-compiled
certain library already installed on my system. This triggered some thoughts
as to how could gentoo support a debugging scenario. Has anyone though of
something in this area?
I'm thinking of something like emerge --with-debug libxml which would then do
most of the same stuff as normal except that it would run ./configure with
- --enable-debug or appropriate options to trigger the gcc -g flag and before
cleaning up the temp/work folder from /usr/portage it would install in a
debug folder the source file so that gdb could find the symbol when debugging
the libxml compiled using that technique.
The problem I hit is that I am unaware how gdb retrieve the source file.
What path he looks for first etc, in order to install the source at the
correct location. Also great would be to have only the source installed and
cleaning the rest (object etc...) unless someone set the maintainer autoclean
to off.
- --
Yannick Koehler
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE9x5QYfuKOJNEyL1URAoW2AJ9PWioN5F3e09aqzq56u93b+klXvgCeK6A8
k272SUk7T4p0bR1snlsPrR8=
=L0D2
-----END PGP SIGNATURE-----
--
gentoo-dev@gentoo.org mailing list
next reply other threads:[~2002-11-05 15:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-05 9:49 Yannick Koehler [this message]
2002-11-05 15:02 ` [gentoo-dev] Feature Request: compiling debug + symbol install ebuild? Paul de Vrieze
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=200211050449.14076.yannick.koehler@colubris.com \
--to=yannick.koehler@colubris.com \
--cc=gentoo-dev@gentoo.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: link
Be 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