|
From: Nicholas N. <nj...@ca...> - 2004-09-12 20:40:49
|
On Sun, 12 Sep 2004, Julian Seward wrote: > Friday night's build went as usual on SuSE 9.1. However, last > night's build produces a memcheck which eats all the memory and > swap and thrashes the machine to hell, even with trivial progs > (ls). Furthermore, this message appears at startup: > > Warning: set address range perms: large range 2147483647, a 1, v 1 > > and it didn't used to. > > Strangely, Tom's nightly builds appear OK, except "standard" (RH 7.2); > not sure if that failure is related or not. > > I've been looking through Saturday's commits, trying to figure out > how this happened. One possibility is vg_mylibc.c:1.90 > (Fix minor off-by-one error), althought that doesn't seem very likely. > > Another one which might somehow mess with memory layout is Tom's > fix to #73818 (stack rlimit stuff). Presumably either I or Tom introduced this yesterday, since we were the only ones making changes. I looked through my commits but couldn't see anything. It's hard to know without knowing which revision caused it. I realise it's a pain diagnosing someone else's breakage, but could you try to work this out? We can't really get anywhere without knowing that. You can use the -D option to checkout trees for a particular time, so for each commit you could checkout before and after the time of the commit, and see if both work ok. N |