On 01/06/10 09:55, Dave Griffiths wrote:
On Sun, 2010-05-30 at 07:44 +0200, gabor papp wrote:
some random memory corruption or race condition is happening - are there
any tips for debugging fluxus with valgrind?
as far as i remember you need to use the
–vex-iropt-precise-memory-exns=yes parameter in valgrind otherwise you
get false alarms. i also had to suppress opengl driver errors, but you
might not get those with nvidia.
Seems like we introduced something recently, or it could be an
interaction between specific versions of plt scheme and fluxus, see
also:
http://www.reddit.com/r/programming/comments/c9epm/programming_music/c0r38o2
Claude - what version of PLT scheme are you running?
I was lazy and just installed from package manager, is it still
essential to compile PLT from source? Fluxus seems to work, apart from
the random segfaults...
plt-scheme:
Installed: 4.2.1-1
Candidate: 4.2.1-1
Version table:
*** 4.2.1-1 0
500 http://gb.archive.ubuntu.com/ubuntu/ lucid/universe Packages
100 /var/lib/dpkg/status
mzscheme:
Installed: 2:4.0.1+fake.2
Candidate: 2:4.0.1+fake.2
Version table:
*** 2:4.0.1+fake.2 0
500 http://gb.archive.ubuntu.com/ubuntu/ lucid/universe Packages
100 /var/lib/dpkg/status
With these files (no mz*.so anywhere afaict):
/usr/lib/plt/mzdyn3m.o
/usr/lib/libmzscheme3m.a
I'll try and find
out what the default version on puredyne is
I just checked the package lists, Puredyne 9.10/9.11 DVDs have:
plt-scheme 4.1.5-1
- as this probably explains
Elmers' problems too.
Claude
