| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
|
| 5 |
Hi, |
| 6 |
|
| 7 |
Recently I hitted a problem with valgrind which required me to re-compiled |
| 8 |
certain library already installed on my system. This triggered some thoughts |
| 9 |
as to how could gentoo support a debugging scenario. Has anyone though of |
| 10 |
something in this area? |
| 11 |
|
| 12 |
I'm thinking of something like emerge --with-debug libxml which would then do |
| 13 |
most of the same stuff as normal except that it would run ./configure with |
| 14 |
- --enable-debug or appropriate options to trigger the gcc -g flag and before |
| 15 |
cleaning up the temp/work folder from /usr/portage it would install in a |
| 16 |
debug folder the source file so that gdb could find the symbol when debugging |
| 17 |
the libxml compiled using that technique. |
| 18 |
|
| 19 |
The problem I hit is that I am unaware how gdb retrieve the source file. |
| 20 |
What path he looks for first etc, in order to install the source at the |
| 21 |
correct location. Also great would be to have only the source installed and |
| 22 |
cleaning the rest (object etc...) unless someone set the maintainer autoclean |
| 23 |
to off. |
| 24 |
|
| 25 |
- -- |
| 26 |
|
| 27 |
Yannick Koehler |
| 28 |
-----BEGIN PGP SIGNATURE----- |
| 29 |
Version: GnuPG v1.0.6 (GNU/Linux) |
| 30 |
Comment: For info see http://www.gnupg.org |
| 31 |
|
| 32 |
iD8DBQE9x5QYfuKOJNEyL1URAoW2AJ9PWioN5F3e09aqzq56u93b+klXvgCeK6A8 |
| 33 |
k272SUk7T4p0bR1snlsPrR8= |
| 34 |
=L0D2 |
| 35 |
-----END PGP SIGNATURE----- |
| 36 |
|
| 37 |
|
| 38 |
-- |
| 39 |
gentoo-dev@g.o mailing list |
Archives