Hazel Russman [2009-09-16 15:43]:
I have a small gtk-based program which puts up buttonbars on my desktop. I have used it in both Crux and Debian and have never had any problems with it. But since upgrading to Crux-2.6, I have had intermittent aborts. The traceback (attached) suggests that the problem is inside libc, specifically in malloc.
Once the program has aborted, it aborts each time it is restarted. But weirdly I was able to break this cycle simply by altering the order in which buttons were created, via the program's config file. For example, this version -
[...]
Is this a bug or am I doing something wrong?
I'm guessing that the program does something wrong, and that the error was tolerated by earlier glibc versions. Try running the program in valgrind; that should give you more clues on where the heap corruption happens resp what causes it. Regards, Tilman -- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail?