[ardour-dev] Development environment

John Emmas johne53 at tiscali.co.uk
Mon Apr 9 08:42:07 PDT 2007

Thanks for the info Mike (and everyone).  I'll take a look at Eclipse
and Emacs as soon as I can.  DDD might be worth looking at, too.
Eclipse seems to be closest to what I'm used to.

> On 4/9/07, Mike Taht <mike.taht at gmail.com> wrote:
> Ardour is a realtime process with many threads. It's almost impossible to
> "step through" anything as there is so much going on at any given point
What happens then, if you need to set a break point in the code?  i.e. how
would you go about doing that and what would happen when the break point
gets reached?

In my experience, it's rare to need to step through more than one thread at
a time (though not unheard of).  Almost all of my Windows apps are multi-
threaded but I've never experienced any problem stepping through the code.
Having said that, communication between threads under Windows works
using message pumps - which is actually quite a good strategy for minimizing
the tendency for threads to be reliant on one another.  It makes debugging
a multi-threaded app relatively pain free - but of course, the downside
is that the technology wouldn't be well suited to a real-time OS.


More information about the Ardour-Dev mailing list