Re: GTK+ 1.2.10 on Solaris has segfault inside malloc



Paul Davis wrote:
your program almost certainly has a bug. i would suggest running it
under valgrind, or an equivalent (*). errors like the one you are seeing
are more or less instantly recognizable to long time programmers as
evidence of memory corruption elsewhere in the program (think "buffer
overrun" or "pointer walk").

--p

(*) valgrind is perhaps the most useful programming tool i have
    discovered in the last 5 years, after libsigc++ :) valgrind is,
    simply put, superb.


Sadly, valgrind seems to be x86 specific, and my problem is on Solaris.

My application was at one point memory-usage-clean, as far as I could determine with the g_malloc facilities and with gskdebug from the gsk (Gnu Server Kit) library. I will try those again and verify that they indicate clean behavior.


Eric




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]