Closed GoogleCodeExporter closed 9 years ago
Is this from a clean build? I can't reproduce it. If a clean build doesn't fix
it, can you try running wmii from valgrind?
Thanks.
Original comment by maglion...@gmail.com
on 26 Jun 2010 at 12:31
Yes, it still occurs with a completely clean build. Attached is valgrind
output.
Original comment by sun...@gmail.com
on 26 Jun 2010 at 2:00
Attachments:
It doesn't seem to indicate a segfault. Or any other memory errors. Did it
crash in that instance?
Also, leak-check=full adds a lot of noise without providing any useful
information. It's possible that I've missed something.
Original comment by maglion...@gmail.com
on 26 Jun 2010 at 2:23
Argh, sorry. I did a clean builds & installs again, testing one commit at a
time, and found that it was the bar file changes causing problems in my wmiirc:
http://hg.suckless.org/wmii/rev/9d31d13386b8
I'll do completely clean builds & installs from here onwards.
Original comment by sun...@gmail.com
on 26 Jun 2010 at 5:05
I think you'll find that running 'make depend' every so often prevents most of
the same problems fixed by clean installs. I guess since that's not part of the
GNU toolchain, only BSD people do it, though.
Also, writing revision 9d31d13386b8 suffices to link a revision. It doesn't
make a difference to me, but it is a bit easier to type.
Original comment by maglion...@gmail.com
on 26 Jun 2010 at 5:12
Oh, and I notice that the Google people finally decided to make their diff
display colourblind friendly... Nice to know.
Original comment by maglion...@gmail.com
on 26 Jun 2010 at 5:14
Original issue reported on code.google.com by
sun...@gmail.com
on 26 Jun 2010 at 12:18