[PD-dev] Pointers changing/corrupting (used to be "signal nan values")

[Andrew Hassall]

also just a bit of information,
contrary to what I said in a previous email, both files are now
assuming no overlap, (to make it simpler for debugging).
and there are lots of seemingly random posts, and outlet floats, again
these are all for debugging.

On Wed, Apr 27, 2011 at 12:17 PM, Andrew Hassall <a.r.hassall at gmail.com> wrote:
> No thats fine, I've attached both c files. (they are a bit messy at
> the moment due to debugging and tearing them apart sorry, if you need
> cleaner commented code I can comment it up no problem)
>
> will that mean that the list would be out of sync with the frames/blocks?
> because the list being outputted is a specific list of filter
> coefficients unique to each particular frame and is needed by the next
> object for it to function correctly. (sorry I don't know much about
> the clock_delay function)
>
> On Wed, Apr 27, 2011 at 11:27 AM, IOhannes m zmoelnig <zmoelnig at iem.at> wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> On 2011-04-27 12:08, Andrew Hassall wrote:
>>>
>>> Anyone have any ideas why the pointer would change so dramatically? Is
>>> it being corrupted? if so any ideas what by?
>>
>> do you mind sharing the complete code?
>>
>> and an unrelated issue with your code:
>> you shouldn't call outlet_list() from within your perform routine;
>> rather, it should be scheduled in the next tick (using
>> clock_delay(0))...of course this will delay the analysis by one block
>>
>> fgmar
>> IOhannes
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1.4.11 (GNU/Linux)
>> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>>
>> iEYEARECAAYFAk23764ACgkQkX2Xpv6ydvQAzQCfZNq2N06FQ3GPAWA89cdUE7W0
>> Ac4An0xrX0Kt7c6dRAqVzIdFLB657b9G
>> =/Ocz
>> -----END PGP SIGNATURE-----
>>
>>
>> _______________________________________________
>> Pd-dev mailing list
>> Pd-dev at iem.at
>> http://lists.puredata.info/listinfo/pd-dev
>>
>>
>