On Mon, Apr 03, 2000 at 10:55:11AM -0500, Paul Wagland wrote: > > > Hi Gilbert, > > Line 666 for me is the same as for you. > ie: > > > That's interesting. What is on line 666 of your file.c? On mine, it's > > > > fdata->next = NULL; > > Yes, I had assumed that fdata was NULL, but have not yet looked at the > situation to actually work out what was going on. I don't still have the > core, but this problem is easily reproducible for me.... :-) > > There, just generated another one....Yep, fdata is NULL. > > Now, why is fdata NULL? Obviously g_mem_chunk_alloc(cf->plist_chunk) > failed, > but why. Further looking indicates that cf is valid, but cf->plist_chunk > probably is not. cf->plist_chunk is currently 0, normally a malloc of 0 > returns NULL. so g_mem_chunk_alloc is probably doing the right thing. cf->plist_chunk should refer to the GMemChunk pointer which has lots of allocated memory from which frame_data-sized chunks handed out. So, we need to track down why cf->plist_chunk is NULL. --gilbert
Powered by MHonArc 2.6.10