Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Hofman <pavel.hofman@ivitera.com>
To: Olivier Guillion - Myriad <olivier@myriad-online.com>
Cc: alsa-devel@alsa-project.org,
	Paul Menzel <paulepanter@users.sourceforge.net>,
	Daniel Mack <zonque@gmail.com>
Subject: Re: A debug version of the ALSA lib?
Date: Fri, 02 Sep 2011 14:26:03 +0200	[thread overview]
Message-ID: <4E60CB5B.3030809@ivitera.com> (raw)
In-Reply-To: <4E60C7A3.369.112627E@olivier.myriad-online.com>

Dne 2.9.2011 14:10, Olivier Guillion - Myriad napsal(a):
> Hi,
> 
> Daniel Mack, then Paul Menzel wrote:
>>>>> Or just use the binary Ubuntu packages and be done.
>>>>
>>>> Sorry, but what does it mean?
>>>
>>> That means that Ubuntu (as many other distros) offers you a
>>> ready-made, debug symbols enabled version of the library which you can
>>> just install and use. As you're struggeling with compiling the library
>>> youself, I'd suggest you go for this solution. In Ubuntu, the package
>>> you're looking for is called libasound2-dev.
>>
>> I have not followed the thread, but if you want debugging symbol you
>> need `libasound2-dbg`. (`aptitude search libasound*`)
> 
> I installed the libasound2-dev package. 
> I got mainly :
> - a bunch of C header files in /usr/include
> - libasound.a, libasound.la and libasound.so in /usr/lib
> (none of these libraries include the debugging symbols)
> 
> I tried "aptitude search libasound*"
> and got:
> libasound-dev
> libasound2
> libasound2-dev
> libasound2-doc
> libasound2-plugin-equal
> libasound2-plugins
> 
> but no libasound2-dbg.
> Any idea about where (and how) I can get it? (using Ubuntu 11.04)
> 

Yes, use the procedure I gave you in
http://permalink.gmane.org/gmane.linux.alsa.devel/88753 . I used it a
few weeks ago to debug alsa-lib in gdb.

Just tested now, ubuntu 10.04:

sudo apt-get build-dep libasound2
apt-get source libasound2
cd alsa-lib-1.0.22/
export DEB_BUILD_OPTIONS=nostrip,noopt
dpkg-buildpackage -rfakeroot -uc -us

Simple check while the compilation runs shows the gcc compiler is called
with -g -O0 params.

In a few minutes fresh .debs were waiting for me in the parent
directory, to be installed with dpkg -i libasound*deb and stepped with gdb.

With regards,


Pavel.

  reply	other threads:[~2011-09-02 12:26 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-01  8:37 A debug version of the ALSA lib? Olivier Guillion - Myriad
2011-09-01  8:50 ` Daniel Mack
2011-09-01  9:00   ` Pavel Hofman
2011-09-01 14:19     ` [Mult]Re: " Olivier Guillion - Myriad
2011-09-01 15:46       ` Daniel Mack
2011-09-01 16:37         ` Olivier Guillion - Myriad
2011-09-01 16:49           ` Daniel Mack
2011-09-02  8:44             ` Olivier Guillion - Myriad
2011-09-02 10:43               ` Daniel Mack
2011-09-02 10:55                 ` Paul Menzel
2011-09-02 12:10                   ` Olivier Guillion - Myriad
2011-09-02 12:26                     ` Pavel Hofman [this message]
2011-09-02 15:43                     ` Paul Menzel
2011-09-02 18:16                       ` David Henningsson
2011-09-02 12:46                   ` Daniel Mack
2011-09-02 13:32                     ` Pavel Hofman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4E60CB5B.3030809@ivitera.com \
    --to=pavel.hofman@ivitera.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=olivier@myriad-online.com \
    --cc=paulepanter@users.sourceforge.net \
    --cc=zonque@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox