[ardour-dev] Ardour segfault - backtrace info

Mark Knecht markknecht at gmail.com
Wed Oct 12 10:09:12 PDT 2005

On 10/12/05, Paul Davis <paul at linuxaudiosystems.com> wrote:
> > 1) Certianly I'd like to know why my session causes this. What can I
> > change to effect this?
> i don't think its your session, its the loop back to zero, i would
> guess. there are 2 issues: why does ardour decide it needs to run a
> process() call with nframes == 0 and secondly, what should ardour do
> when it does decide to try this?

Is there any guidance that you can give about why my session would
even be asking Ardour to do this? What did I do 'wrong' in Ardour's
mind? How can I debug that a bit more?

> > 2) I guess you'll add some sort of check in the future, but with the
> > state of changes right now I think CVS may be of no use to me? Is this
> > correct? Or can I look for a fix in a nightly tarball sometime soon,
> > assuming I cannot fix the session myself.
> there will be no changes to CVS for the ardour 0.99 line until the first
> ardour2 version compiles.

Fair enough, but the problem is real so if you want me to test a patch
here please let me know.


More information about the Ardour-Dev mailing list