On Thu, 05 Aug 2004 23:04:49 -0700
davidrclark@xxxxxxxxxxxxx wrote:
> I found that I can set ulimit -l to some fraction of memory so that
> it isn't "unlimited." This does produce various warnings, but on this
> machine, with what little I've done thus far, MusE *seems* to run OK.
> It would seem to me, with what little I know about mlock() policy, that
> there is an mlock() SNAFU in some of the Linux audio programs. If
> that's not the case, I'd really like to hear the explanation. (Thanks
> to anyone who contributes info on this.)
For memory problems, the first step would be to run the app under
valgrind to check for memory leaks and usage of unitialised data.
Unfortunately, I don't think valgrind works on the 2.6 kernel yet.
Maybe you could boot a 2.4 kernel to test this.
With valgrind you basically do something like:
valgrind -v --leak-check=yes
which might have some interesting info.
Erik
--
+-----------------------------------------------------------+
Erik de Castro Lopo nospam@xxxxxxxxxxxxx (Yes it's valid)
+-----------------------------------------------------------+
"What lawyers call 'intellectual property' is -- as every Latin student
knows -- no more than theft from the public domain."
-- Andy Mueller-Maguhn, newly elected ICANN board member for Europe.
