| 1 |
On Sat, Jun 23, 2012 at 6:08 PM, Michael Mol <mikemol@×××××.com> wrote: |
| 2 |
> https://bugs.gentoo.org/show_bug.cgi?id=423149 |
| 3 |
|
| 4 |
As it turned out, it was my CFLAGS. Not the ones anyone usually cares |
| 5 |
about, either. |
| 6 |
|
| 7 |
If you build glibc with CFLAGS="${CFLAGS} -g3", your glibc will be |
| 8 |
very, very broken. Apparently, it's old, known and has been a problem |
| 9 |
for about five years.[1] |
| 10 |
|
| 11 |
Which means that when I changed my CFLAGS from "-ggdb" to "-ggdb3" a |
| 12 |
few months ago, the next time I emerged glibc was going to be the time |
| 13 |
that killed my system. I didn't think twice about it at the time, |
| 14 |
either; When trying to debug something, how often does it turn out to |
| 15 |
be the debugging *data* that's causing the problem? I'm accustomed to |
| 16 |
systems behaving differently with debuggers attached, but this |
| 17 |
was...bizarre. |
| 18 |
|
| 19 |
The other big thing I kept hearing about was "try changing |
| 20 |
{this|that|other thing}; it might be affecting glibc, because glibc is |
| 21 |
a whiny b*tch". Are there alternatives to glibc? |
| 22 |
|
| 23 |
Meanwhile, while trying to accelerate the tweak/retry cycle of testing |
| 24 |
this, I wrote a script which automatically installs, configures, |
| 25 |
updates and builds Gentoo. I'll share it on github soon enough; it's |
| 26 |
got a bunch of pieces which are particular to my use case. Just a |
| 27 |
couple more changes before it generates a clean, configured system |
| 28 |
(for me). Once I've got a stable, working box at home, I'll be able to |
| 29 |
refine it. |
| 30 |
|
| 31 |
[1] http://twitter.com/flameeyes/status/217361466158874626 |
| 32 |
|
| 33 |
-- |
| 34 |
:wq |
Archives