atom feed11 messages in at.iem.pd-listRe: [PD] [PD-announce] pd 0.43-1 test...
FromSent OnAttachments
Miller PucketteNov 6, 2011 10:55 pm 
João PaisNov 7, 2011 4:00 am 
IOhannes m zmoelnigNov 7, 2011 4:24 am 
Hans-Christoph SteinerNov 7, 2011 7:43 am 
Roman HaefeliNov 11, 2011 4:57 am 
Hans-Christoph SteinerNov 11, 2011 8:05 am 
Roman HaefeliNov 13, 2011 6:58 am 
Miller PucketteNov 13, 2011 9:17 am 
Mathieu BouchardNov 13, 2011 9:55 am 
Roman HaefeliNov 13, 2011 11:45 am 
Mathieu BouchardNov 13, 2011 12:55 pm 
Subject:Re: [PD] [PD-announce] pd 0.43-1 test 5 released
From:Mathieu Bouchard (mat@artengine.ca)
Date:Nov 13, 2011 12:55:58 pm
List:at.iem.pd-list

Le 2011-11-13 à 20:45:00, Roman Haefeli a écrit :

Can you also post Valgrind backtraces for all the Invalid Writes ?

How does it help to also have the Valgrind backtrace?

In case the bug is more subtle than GDB can find.

GDB finds only the final consequences, whereas Valgrind usually finds an early cause. For some bugs, it does not matter.

I think I posted all the necessary information to make Pd crash.

It's often not sufficient to cause a crash.

Perhaps even any related warnings (but note that Valgrind always provide a bunch of unrelated warnings).

Is it something like that it considers Pd's symbol table to be a memory leak because it gets never freed as long as Pd is running? I'm not sure, but I vaguely remember you saying something the like.

That's only if you enable the leak-checker, and that thing is off by default, and should be kept off while looking for the cause of a crash.

Why are you asking? Are you going to help fix this?

Nevermind, then.

______________________________________________________________________ | Mathieu BOUCHARD ----- téléphone : +1.514.383.3801 ----- Montréal, QC

_______________________________________________ Pd-l@iem.at mailing list UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list