Hi! > Sorry for such a long gap. I tried finding out that why that test case was > failing by running a normal C program with malloc implementation. > > I found that, when I am trying to allocate a smaller memory chunk, memory > is getting allocated from the same address, but for a larger memory chunk, > it is allocating from some different address i.e if condition is getting > true (that means that test is failing). > Couldn't figure out, why this difference. Any idea on to where should I > look into?
Well as far as I know very large chunks are not allocated on the heap but using anonymous mmap() (wikipedia suggests that usual threshold value is 256KB). In such case having two different addresses would not idicate a bug as expecting deterministic behavior from mutitasking preemptive kernel is simply wrong. > And yes, I will surely try to fix if this is a broken test. But moreover, > in some other kernel version it was passing. So, need to figure out as to > what changes has been made for this. I've been faster than you ;). I've commited a patch that removes this part of the test yesterday. -- Cyril Hrubis [email protected] ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct _______________________________________________ Ltp-list mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ltp-list
