On Fri, Feb 24, 2012 at 12:53 PM, Carsten Haitzler <[email protected]> wrote: > On Fri, 24 Feb 2012 20:49:31 +0900 Kim Shinwoo <[email protected]> said: > > ok - address seems quite low. that should be an address inside a mmaped file.
>> Just before the segmentation fault .. s1 and s2 are belows... >> >> > s1=0x570ba5* <Address 0x570ba5 out oo bounds>* >> > s2=0x639db184 "edje/file" >> >> > Program received signal SIGSEGV, Segmentation fault. Hum, s1 and s2 should be in the same mmaped file, so almost the same adress. That's obviously not the case. Possible problem could come from a invalid chained list in eet hash (so something to look in find_node_by_name). But this solution seems impossible as this is only possible if calloc didn't set memory to zero... The second problem that I don't understand, is that when we load from a file, we check that the mmaped string is really a NULL terminated string of name_size length. Maybe you could print the content of efn->name_size in find_node_by_name. But I really don't understand how this pointer could get in and pass all this check... -- Cedric BAIL ------------------------------------------------------------------------------ Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
