On Tue, Oct 29, 2013 at 11:20:14PM +0200, utku genç wrote: > Probably you are right. But I will post this anyway, maybe you will catch > something else.
Compiling with "-fstack-protector-all" might help (depends on what is actually happening, maybe it doesn't help at all) to see where the problem is. It basically adds some guards when you call/exit a function and check that everything is the same. If it's not, it prints an error and exits instead of having the stack corrupted and realize about it (potentially) later. Thanks, Rodrigo _______________________________________________ libev mailing list [email protected] http://lists.schmorp.de/cgi-bin/mailman/listinfo/libev
