Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#924 consistency check failed: gstack_pop

v0.42
open
nobody
puredata (318)
5
2012-10-07
2012-10-06
Anonymous
No

1. launch pd
2. crreate a new patch
3. create a new object [r #X]

on creation pd console displays
consistency check failed: gstack_pop

if after step 3 and autoconnect is enabled, you

4. create [print foo]

you see additionally

foo: connect 0 0 1 0

in the console.

subsequent actions don't seem affected
but "check failed" sounds srsly hairy
though it might not be actually dangerous?

Discussion

  • you just discovered the internals of Pd....whenever a patch is loaded, the entire patch-file is sent to the "#X" receiver.
    there are a number of "reserved" receivers, none of them documented and all starting with a '#'.

    in short: you should not use receivers that start with "#".

    as for the warning: i checked with Pd-0.43.2 and i don't get this error. most likely it was fixed.

     
  • (not the author)

    ..can it be that you can mess up pd when using them?! I just did and I eg. pasted always 2 objects at the same time while I copied only one.
    Ok again after restart..

    Are they useful for dynamic-patching??

     


Anonymous


Cancel   Add attachments