[PD-dev] broken msgs cause Tcl traces, how to debug it?

[Mathieu Bouchard]

Le 2012-01-22 à 21:16:00, Miller Puckette a écrit :

> Quick guess; the socket itself (at the OS level) has a fixed buffer size
> and if the sending process exceeds it it is suspended until the receiving
> process eats at least some of it.

AFAIK, that's 4k or 8k for «unix» type (pipe or fs socket) and it might be 
32k for TCP sockets. But code must not rely on specific buffer sizes.

>> If you remove the [info complete] bracket from pd_readsocket, there are 
>> these intermittent Tcl stacktraces causes by messages from 'pd' to 
>> 'pd-gui' that get split in the wrong spot.

yes, [info complete] is a potential major slowdown because it may reparse 
code many times while the amount of code increases. It's a n² time order 
thing.

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