Hello, Great investigation ! In the 1.1.0 release I use the bug was fixed (I did not remember), that 's why it could not happen, even with valgrind. Thanks
Simon Le Jeudi 25 Août 2005 16:18, Martin Samuelsson a écrit : > Simon Morlat @ 2005-08-24 (Wednesday), 23:27 (+0200) > > > Hello, > > Hi there, > > > For now I have no idea. I'll try reproduce the bug with valgrind. > > That's an idea I never though of, and silly enough it still chrashes for > me when running it through valgrind. :/ > > I'm not an total expert on valgrind either, but my expection was that a > memory access error shouldn't result in a chrash... > > Spending a few minutes actually stepping through with gdb made me find > something suspicious. Applying the attached patch fixes the problem for > me, but I guess it's time to do an audit if more things are coded the > way that they assume g_list_free() should NULL the pointer. > -- > /Martin
