Re: glib memory allocation problems

On Fri, 11 May 2007 13:55:25 +0200 (CEST)
Tim Janik <timj gtk org> wrote:
> it's likely that some code portions erroneously use GSlice and thus screw
> up the memory handling at some point. G_SLICE=debug-blocks is really the
> recommended way to find those errors and much faster than trying
> valgrind (and definitely more accurate about slices).


I reproduced the crash using G_SLICE=debug-blocks, this time using a different usage scenario (the one described at ). Unfortunately the program didn't output any debugging text like the one you describe in your blog. So I got another backtrace and kept that coredump too so that I can run any command you tell me. 

So does the attached backtrace means anything to you? 

Thanks in advance, 

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