On 2010/10/28 15:46, Adrian Knoth wrote:
> Can you confirm that test.c doesn't trigger the bug when ffado is
> compiled without DEBUG?
Confirmed. The package 2.0.1+svn1856-6 hides the symptoms of the bug.
(The bug is of course still present, and needs to be fixed)
Max
__
On Thu, Oct 28, 2010 at 01:54:25PM +0200, Max Kellermann wrote:
> > When I compare
> >
> >
> > http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=5;filename=test.c;att=1;bug=601657
> >
> > to the code in jackd1's drivers/firewire/ directory or to ffado's
> > tests/streaming/teststreaming3.cpp,
On 2010/10/28 13:44, Adrian Knoth wrote:
> When I compare
>
>
> http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=5;filename=test.c;att=1;bug=601657
>
> to the code in jackd1's drivers/firewire/ directory or to ffado's
> tests/streaming/teststreaming3.cpp, I wonder if you might simply miss to
On Thu, Oct 28, 2010 at 11:41:50AM +0200, Max Kellermann wrote:
> > > ERROR: messagebuffer not initialized: 1250338856611: [31mWarning
> > > (ffado.cpp)[ 121] ffado_streaming_init: Realtime scheduling is not
> > > enabled. This will cause significant reliability issues.
> >
> > You're running it
Processing commands for cont...@bugs.debian.org:
> reopen 601657
Bug #601657 {Done: Adrian Knoth } [libffado2]
libffado2 thread crashes with assertion failure
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
601657: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug
reopen 601657
thanks
On 2010/10/28 11:08, Adrian Knoth wrote:
> On Thu, Oct 28, 2010 at 09:31:48AM +0200, Max Kellermann wrote:
>
> > The attached test program can trigger a (timing?) bug in libffado2,
>
> Welcome to userlevel device drivers. For some reasons, the packets were
> not delivered o
Package: libffado2
Version: 2.0.1+svn1856-5
Severity: serious
The attached test program can trigger a (timing?) bug in libffado2,
which causes an assertion failure (i.
