| 1 |
On 5/1/06, Graham Murray <graham@×××××××××××.uk> wrote: |
| 2 |
> In the 'debugging' howto referenced in this week's GWN it mentions the |
| 3 |
> CFLAGS and setting FEATURES to either nostrip or splitdebug. However, |
| 4 |
> there is also a global 'debug' USE flag. Should this also be set if |
| 5 |
> setting CFLAGS to include -g and FEATURES splitdebug in |
| 6 |
> /etc/make.conf? |
| 7 |
|
| 8 |
Generally I would answer 'no', but this depends upon how much |
| 9 |
debugging you want to do. The splitdebug setting is sufficient to get |
| 10 |
good stack traces in the event of a program crash. |
| 11 |
|
| 12 |
The debug USE flag will do different things for different packages. |
| 13 |
But it generally falls into one of two categories: |
| 14 |
|
| 15 |
1. Enable extra logging of the package. For example, emerging wine |
| 16 |
without debug will disable call tracing, making it difficult to file |
| 17 |
bug reports or figure out what native vs windows dlls you should be |
| 18 |
using for a particular program. |
| 19 |
|
| 20 |
2. Enable extra checks in the code. Things like assertions, type |
| 21 |
checks, and array boundary checks. These extra checks can have a |
| 22 |
significant impact on performance. The glib and gtk packages fall |
| 23 |
into this category. |
| 24 |
|
| 25 |
-Richard |
| 26 |
|
| 27 |
-- |
| 28 |
gentoo-user@g.o mailing list |
Archives