octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Audiorecorder/Player segfault


From: Vytautas Jancauskas
Subject: Re: Audiorecorder/Player segfault
Date: Mon, 29 Jul 2013 22:41:41 +0300

On Fri, Jul 26, 2013 at 2:00 AM, Pantxo Diribarne
<address@hidden> wrote:
> Le 25/07/2013 22:24, Vytautas Jancauskas a écrit :
>
>> On Thu, Jul 25, 2013 at 9:33 PM, Michael Goffioul
>> <address@hidden> wrote:
>>>
>>> On Thu, Jul 25, 2013 at 1:59 PM, pantxo diribarne
>>> <address@hidden> wrote:
>>>>
>>>> Attached is an octave session run through valgrind.
>>>> Let me know  if I can run any other blind test.
>>>
>>>
>>> This specific message:
>>>
>>> Address 0x106c19a40 is 0 bytes after a block of size 708,608 alloc'd
>>>
>>> indicates an attempt to read outside of an allocated buffer (see [1]).
>>> The
>>> valgrind output contains information about where the memory alloc took
>>> place
>>> and where the invalid read is happening.
>>>
>>> Michael.
>>>
>>> [1] http://valgrind.org/gallery/linux_mag.html
>>>
>> Does the segfault only ever happen when using audioplayers initialized
>> from audiorecorders?
>
> No, octave also crashes if I retrieve the data and then initialize
> audioplayer :
>
> ar = audiorecorder ();
> record (ar, 2); # recordblocking makes no difference
> y = getaudiodata (ar);
> ap = audioplayer (y, ar.SampleRate);
> play (ap);
>
>
> Sometimes it's a "segmentation fault: 11", sometimes a "bus error: 10".
>
> Pantxo

Yet it does not happen if you try to play data attained otherwise? That's odd.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]