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