> James> intresting this is your printf's dont line up with what has > James> been printed. > > Are you suggesting that the fprintfs are not being flushed? Why do > you think this would happen? > Most of the outputs like stdout stderr are line buffered until you program configures them otherwise. Your printf's were like this fprintf (stderr, "%u ", totalmalloc); So it could fail somewhere between the first and last fprintf. > James> What should really happen is that something should be killed by > James> the kernel's oom killer or the malloc should fail. But if its > James> overcommiting the malloc will never fail. > > My process is not being killed, because I have disabled the OOM > killer. What I really want to do is set > /proc/sys/vm/overcommit_memory to 2, but the problem with that is bash > won't even execute normal programs, even though I have 32MB of ram! You may also need to increase the amount of free memory the kernel will try to hold. James -- Kernelnewbies: Help each other learn about the Linux kernel. Archive: http://mail.nl.linux.org/kernelnewbies/ FAQ: http://kernelnewbies.org/faq/
