Bug#584605: audacity: Continuing to backtrace

[Adrian Knoth]

On Tue, Jun 15, 2010 at 02:30:52AM -0400, Dave Witbrodt wrote:

> (I really wish that I could bisect using 'git'.  Does the 'audacity'  
> upstream use 'git', or do the Debian maintainers have their own 'git'  
> repo where they merge new versions from upstream?  I am merely a  

   http://packages.qa.debian.org/a/audacity.html

See the VCS link on the left, there it is.

The easy way:

   $ debcheckout audacity

This clones you the corresponding git repository.

debcheckout is in the devscripts package.

> beginner with tools such as 'git' and 'gdb', but I did spend a month  

Given that you have a memory issue here, I'd like to recommend valgrind.
That's a nice tool to spot out of bound access and the lot.

> Miracle of miracles!  Version 1.3.5 runs fine on my system -- no changes  

No miracle at all, they changed the code in px_linux_alsa.c. git bisect
will tell you about it.

You might also want to have a look at the upstream svn and read the
commit messages:

   http://code.google.com/p/audacity/source/browse/audacity-src/trunk



Good luck. ;)

-- 
mail: adi at thur.de  	http://adi.thur.de	PGP/GPG: key via keyserver