Re: [PD-dev] external crashing when block size changes

2023-09-20 Thread IOhannes m zmölnig
Am 20. September 2023 09:07:18 MESZ schrieb Alexandros Drymonitis : >Both of you were right. The 2 wasn't necessary, and indeed, I forgot to >multiply by the element type. > Actually I assumed that "2" was meant to be the element size, and thus plain wrong (it would be "4" on single

Re: [PD-dev] external crashing when block size changes

2023-09-20 Thread Alexandros Drymonitis
Both of you were right. The 2 wasn't necessary, and indeed, I forgot to multiply by the element type. Thanks for the casting to t_int tip, wasn't aware of that. On 9/19/23 23:17, Christof Ressi wrote: what is this "2" supposed to represent? This looks like a mistake to me. The buffer

Re: [PD-dev] external crashing when block size changes

2023-09-19 Thread Christof Ressi
what is this "2" supposed to represent? This looks like a mistake to me. The buffer certainly does not have to be twice as large, as it is only used to copy the input. To solve the mystery, you don't allocate the right amount of memory because you forgot about the element type: x->bufbytes

Re: [PD-dev] external crashing when block size changes

2023-09-19 Thread IOhannes m zmölnig
On 9/19/23 20:02, Alexandros Drymonitis wrote:     x->bufbytes = x->chnls*2*sp[0]->s_n; what is this "2" supposed to represent? mfdsar IOhannes OpenPGP_signature Description: OpenPGP digital signature ___ Pd-dev mailing list

[PD-dev] external crashing when block size changes

2023-09-19 Thread Alexandros Drymonitis
I'm trying to create a signal external with a variable number of inlets and outlets. As a test, I have written an object that copies its input to the respective output. When I put the object in a subpatch and use [block~] to change the block size, it crashes. Loading Pd with gdb gives the