On Thu, 3 May 2012 23:18:01 +0100, andy pugh wrote: > On 3 May 2012 23:01, John Morris <j...@zultron.com> wrote: > >>> 3) freeing up memory that was allocated by one >>> process but still accessing it in a different one. Anyway that is >>> my >>> personal experience. YMMV. >> >> I'm sure that's right. However, it requires familiarity with the >> code >> that I don't have to find that sort of thing, > > Easy test, comment out all the "free" or "kfree" statements (possibly > one at a time, to find the offender). > You will introduce a memory leak, so it isn't a true "fix" but to an > extent, so what?
well that could cause a HUGE problem, but if you are just using it to find *which* (k)free is causing the problem... EBo -- ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
