| 1 |
On Fri, Jul 08, 2005 at 11:08:20AM +0900, Chris White wrote: |
| 2 |
> After seeing the strange and unusual postings that we get sometimes in |
| 3 |
> bugzilla.. We've had it! |
| 4 |
Some comments after reading it. |
| 5 |
|
| 6 |
Flags: |
| 7 |
------ |
| 8 |
Please provide an example of CFLAGS/CXXFLAGS for users, possibly in the |
| 9 |
code listing of 'Re-emergeing a package with debugging'. |
| 10 |
|
| 11 |
FEATURES="nostrip" CFLAGS="-O2 -pipe -ggdb3" CXXFLAGS="-O2 -pipe -ggdb3" emerge package |
| 12 |
|
| 13 |
-ggdb3 is more useful that just plain -g (-g expands to -ggdb1 on most |
| 14 |
arches), as it includes #define stuff and some C++ things that can |
| 15 |
be very hard to decipher with just plain -g. |
| 16 |
|
| 17 |
Core dumps: |
| 18 |
----------- |
| 19 |
Also, please point out the value of setting the core-dump ulimit to a |
| 20 |
reasonable size, and backtracing a core-dump instead of the application |
| 21 |
directly. This is esp. applicable for things like mod_php where you |
| 22 |
can't really run the binary directly under gdb. |
| 23 |
|
| 24 |
Just basically set the core-dump ulimit (either commandline or via the |
| 25 |
ulimit configurations), and then run the application, and afterwards do: |
| 26 |
gdb ./bad_core COREFILE |
| 27 |
|
| 28 |
Emerge errors: |
| 29 |
-------------- |
| 30 |
Some builds, esp. PHP include a message in the final emerge message |
| 31 |
(prefixed with !!) telling you to include a specific file (config.log |
| 32 |
most often) with your bug report. Please mention this, and remind users |
| 33 |
it is important! |
| 34 |
|
| 35 |
-- |
| 36 |
Robin Hugh Johnson |
| 37 |
E-Mail : robbat2@××××××××××××××.net |
| 38 |
Home Page : http://www.orbis-terrarum.net/?l=people.robbat2 |
| 39 |
ICQ# : 30269588 or 41961639 |
| 40 |
GnuPG FP : 11AC BA4F 4778 E3F6 E4ED F38E B27B 944E 3488 4E85 |
Archives