Hi Orm, did you get these overflows also with other versions of 0.38 or the devel branch? I ask this because i introduced a more portable version of stack checking that keeps track of the recursion depth instead of the stack pointer. The old method was not compatible with e.g. Python which uses a lot of stack space. To my knowledge the default recursion depth is 1000. That basically means that a message can run through 1000 objects, but depending on the message handling of the object this can also be reduced by some small factor. I would suggest that the method of stack checking should be a compilation switch. Meanwhile you could try to uncomment "#define NEWSTACKMETH" in m_obj.c, line 13.
best greetings, Thomas
----- Original Message ----- From: "Orm Finnendahl" finnendahl@folkwang-hochschule.de To: pd-list@iem.kug.ac.at Sent: Monday, December 13, 2004 9:49 PM Subject: Re: [PD] making object ids visible
Am 13. Dezember 2004, 15:44 Uhr (+0100) schrieb Tim Blechmann:
- test miller's approach of limiting the size of messages sent to the
gui, implemented in 0.38 ... works fine for me ...
I see. Maybe that's also the reason why I now (0.38-13) get a stack overflow much earlier than before. Reading out large datastructs I have to put a 'del 0' every 20th item or so. Before it could be more than 1000.
Has the stack size been decreased in favor of meeting audio deadlines?
-- Orm
PD-list@iem.at mailing list UNSUBSCRIBE and account-management ->