octave-maintainers
[Top][All Lists]
Advanced

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

Re: Audiorecorder/Player segfault


From: Pantxo Diribarne
Subject: Re: Audiorecorder/Player segfault
Date: Fri, 26 Jul 2013 01:00:01 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130623 Thunderbird/17.0.7

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


reply via email to

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