Re: [Csnd-dev] Possible bug in init time array output UDO

yes, there is a bug we have fixed in a PR which I think is related.

best
Prof. Victor Lazzarini
Maynooth University
Ireland

> On 7 Dec 2025, at 23:34, Richard Knight <[email protected]> wrote:
> 
> Hi
> I'm using the latest commit and noticed that a UDO defined like the following causes a segfault with "free(): invalid pointer"
> 
> opcode test1, i[]i, 0
>        iout[] fillarray 1, 2, 3
>        inum = 123
>        xout iout, inum
> endop
> 
> instr 1
>        iout[], inum test1
> endin
> 
> 
> 
> This only seems to happen if a primitive follows an array (i[]i and ii[]i do not work, but ii[] and i[]i[] work OK), and only occurs with init parameters, the same at k-rate works OK.
> Shall I raise this as a bug on github?
> 
> thanks
> RK