Bug#342156: ladspa-sdk: valgrind errors with sine plugin

2006-01-08 Thread Junichi Uekawa
Hi, > > Is there a real point in applying this change or is this just to appease > > valgrind ? > > > > regards, > > junichi > > It's mainly to keep valgrind quiet, but I guess there could be some platforms > where using delete[] on malloced memory could crash. > Current implementation of

Bug#342156: ladspa-sdk: valgrind errors with sine plugin

2006-01-08 Thread Rob Walker
On Sunday 08 January 2006 02:50, Junichi Uekawa wrote: > Hi, > > > Running valgrind on a program that uses the sine.so plugin in this > > package produces the following errors: > > Thanks for the patch. > > > This is due to the plugin allocating strings with strdup, but freeing > > them with delete

Bug#342156: ladspa-sdk: valgrind errors with sine plugin

2006-01-07 Thread Junichi Uekawa
Hi, > Running valgrind on a program that uses the sine.so plugin in this package > produces the following errors: Thanks for the patch. > This is due to the plugin allocating strings with strdup, but freeing them > with delete[]. The attached patch fixes this, using free() to free the > string

Bug#342156: ladspa-sdk: valgrind errors with sine plugin

2005-12-05 Thread Rob Walker
Package: ladspa-sdk Version: 1.1-2 Severity: normal Tags: patch Running valgrind on a program that uses the sine.so plugin in this package produces the following errors: $ valgrind analyseplugin /usr/lib/ladspa/sine.so ==10056== Mismatched free() / delete / delete [] ==10056==at 0x1B