[Boost-build] Memory profiling unreliable?

From: Vladimir Prus (ghost_at_[hidden])
Date: 2006-04-07 10:39:43

Hi,
it seems that memory profiling in bjam is not 100% reliable. Here's what I 
did:

1. Create a simple Python script:

for i in range(0, 7000):
    print "obj target_%d : a.cpp ; " % i

2. Run it, redirecting output to "Jamroot"

3. Create empty file "a.cpp"

4. Run "bjam -n -d+10 > profile"

5. The profile has:

    0  214010000          0     0.000000 1056312754 1056312754 [TOTAL]

that's 1 056 312 754 bytes of memory. In practice, bjam does not take more 
that 150 M of memory. What could be the problem?

- Volodya