1 |
Il 17/12/2012 11:11, Tomáš Chvátal ha scritto: |
2 |
> Hi lads, |
3 |
> lately I am having bit of problems from getting relevant debug info from users. |
4 |
> |
5 |
> Since we already have splitdebug for quite time (and I suppose quite |
6 |
> few of us are using it) how about making it to default profiles |
7 |
> default enabled and add -g to default cflags. Currently it is only |
8 |
> enabled in the developer profile. |
9 |
> |
10 |
> This results in 2 gb data in /usr/lib/debug for my system which is not |
11 |
> that bad with current disk sizes and it saves users quite some time |
12 |
> when i have to request them to recompile half of their system with |
13 |
> debug info just to get idea how to fix their issue. |
14 |
> |
15 |
> I would go even for compressdebug feature but that one needs more time |
16 |
> as some packages like glibc fails to merge with it and you need newer |
17 |
> gdb to work with it. |
18 |
> |
19 |
> Cheers |
20 |
> |
21 |
> Tom |
22 |
> |
23 |
|
24 |
By the way gcc-4.8 will have support for -gsplit-dwarf, should be |
25 |
something similar to split-debug, just done pre linking and with |
26 |
different file names. |
27 |
While I've no idea how this feature work, probably start planning would |
28 |
be beneficial. |
29 |
|
30 |
-gsplit-dwarf |
31 |
Separate as much dwarf debugging information as possible into a |
32 |
separate output file with the extension .dwo. |
33 |
This option allows the build system to avoid linking files with |
34 |
debug information. |
35 |
To be useful, this option requires a debugger capable of reading |
36 |
.dwo files. |
37 |
|
38 |
|
39 |
|
40 |
Also thinking about this a bit more, seem a binpkg for debug stuff can |
41 |
be interesting, similarly to how binary distro do. |
42 |
rogue example implementation: |
43 |
with FEATURE="buildpkg split-debug-pkg" |
44 |
all the /usr/lib/debug and /usr/src/debug files are put in a separate |
45 |
package debug/category/pn or similarly to sec-policy/selinux* debug/cat--pn |
46 |
the user can then install debug packages at will, the dependancies |
47 |
should work (and clone those of the real package) but not be mandatory. |
48 |
|
49 |
how difficult would be to implement this in portage (keep in mind that |
50 |
packages are coupled and should stay that way also for unmerge and |
51 |
whatever)? |
52 |
Would be possible to have FEATURE=" -buildpkg split-debug-pkg"? |
53 |
|
54 |
A similar feature would be useful for linguas support but more difficult |
55 |
to implement. |