This is the mail archive of the guile@cygnus.com mailing list for the guile project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Ole Myren R|hne <mrohne@mixing.uio.no> writes: > > Marius Vollmer writes: > > > > How do you watch the memroy size? With "top"? Top usually displays > > the size of a process in multiples of 1K, I think. And anyway > > externally visible memory grow should come in larger blobs than 16 > > bytes I think. > > I did: > > (do ((i 0 (+ i 1))) > ((= i 102400)) > (dynamic-unlink (dynamic-link "./mysin.so"))) > > and divided the resulting increase by 100K (Surprise;-). Ahh, I see. > Fine! If you replace your infinite loop by a finite loop, you'd be > able to report to the libdl implementors how much memory each > invocation leaks;-) Yes, but somehow, I don't really care. Glibc (aka libc6) has a brand new dlopen implementation I guess, and I don't bother to report bugs against libc5.