[Ardour-Users] Struggling to do anything at all

[John Emmas]

Sampo / Thomas,

Thanks for those links guys.  It's getting a bit late here today but I'll be
sure to investigate them tomorrow.


Kevin Cosgrove wrote:
> > someone in the software group created a program that would spew
> > sequences of individually legal events at the various interfaces
> > while recording those events.  The sequence of events was often
> > nonsensical, but each even was legal.  They found and squashed a
> > ton of bugs using this tool.
> >
Kevin - that's a weird co-incidence.  One of my first 'proper' programs was
a tool that did exactly the same thing (and oddly enough, for a DAW).  It
was back in the late 1980's and communicated with the DAW via RS232.  It
would record all the events so they could be repeated.  As (bad) luck would
have it, the main problem with the DAW was that some bright spark had
specified memory chips that were too slow and most of the problems were
caused by that.  Consequently, the problems weren't repeatable, even on the
same machine, let alone across different machines.  Ultimately my great
'proofing tool' turned out to be useless but I had fun writing it...!

Cheers,

John


----- Original Message ----- 
From: "Sampo Savolainen" <v2 at iki.fi>
To: "John Emmas" <johne53 at tiscali.co.uk>
Cc: <ardour-users at lists.ardour.org>
Sent: 02 August 2007 16:47
Subject: Re: [Ardour-Users] Struggling to do anything at all


> On Thu, 2007-08-02 at 17:29 +0000, John Emmas wrote:
>> >> Paul Davis wrote:
>> >> comments like this enrage me. the fact that YOU cannot understand
>> >> how to single-step through code doesn't mean that we do not.
>> >> we even put up a web page on how to use gdb to debug ardour, and
>> >> anyone who knew how to use gdb in general could use that to single
>> >> step
>> >>
>> I beg to differ Paul.  When you last emailed me about this, I visited the
>> debugging page but all it refers to is how to generate logs & back
>> traces.
>> I did ask some other developers for some guidance about single-step
>> debugging (because personally, I use it all the time).  But I couldn't
>> find
>> anyone who even felt the need for it - let alone who knew how to do it.
>> If it's possible, please let me know how to do it - because I'm not going
>> to
>> delve into any Ardour code until I know it can be done.
>
> The gdb page was created to encourage normal users to send us
> backtraces. It is not meant as a complete manual for gdb. That is
> available either via googling: gdb manual
>
> (That search will bring this up as the first hit
> http://sourceware.org/gdb/documentation/ )
>
> Single step debugging is easy in gdb. Once you are in gdb, you just
> either "step", "next" or "continue". Each of these commands can be
> abbreviated to a single character. So s<enter> will step once. Pressing
> enter without any command will repeat the previous one.
>
>
>
> Sampo
>
>
>
>