[alsa-devel] [Mult]Re: A debug version of the ALSA lib?

Olivier Guillion - Myriad olivier at myriad-online.com
Thu Sep 1 16:19:42 CEST 2011

Thank you!

Unfortunately, it didn't work for me.
It started to install about 700 MB of miscellaneous packages, and failed on the 
making of the final package.
By precaustion I reverted to a previous snapshot of my system.
Isn't it a simpler way to get debug info?
Is it possible for instance to install libasound-dbg on Ubuntu 11.04?

Maybe my problem comes from run-time link with the library?
Does anyone use Code:Blocks to compile C applications that use ALSA?

If yes could you please tell  me the compiler/linker settings to properly use 
the ALSA shared libs? I added "/usr/lib/libasound.so.2" to the "Link library" 
section of the Linker settings, and it worked, but I still get crashes on the 
"snd_device_name_hints", especially within a small Mozilla plug-in in Firefox.

I can send the whole project, with a very easy test that shows the problem if 


Pavel Hofman <pavel.hofman at ivitera.com> wrote :

> >> To be able to go further, I'd need a debug version of the ALSA library,
> >> including variable names and source lines, which could let me find more
> >> easily what goes wrong and when.
> >>
> >> Is it possible to build such a library from the alsa-lib- sources? Or
> >> should I download and install another specific package?
> > 
> > The sources are the same. Whether you'll get a library with debug
> > symbols depends on the compile time options when building the lib. And
> > depending on your distribution, you might also be able to install the
> > debug-enabled version by choosing the -dbg package derivat.
> E.g. in debian/ubuntu I use dpkg-buildpackage with debug enabled, for
> details see e.g.
> http://jameswestby.net/tips/tips/compiling-debian-package-for-debug.html
> , just libasound2 instead of mutt.

More information about the Alsa-devel mailing list