Mitul Sen (misen) wrote:
Hi,
-----Original Message----- From: stan [mailto:ghjeold_i_mwee@cox.net] Sent: Wednesday, July 23, 2008 11:26 AM To: Mitul Sen (misen) Cc: alsa-devel@alsa-project.org Subject: Re: [alsa-devel] Setting format to SND_PCM_FORMAT_MU_LAW does not let me apply hardware parameters
Mitul Sen (misen) wrote:
Hi,
I have tried using gdb both from the command line as you
suggested and
also from within eclipse. Even though I can step through
the code and
break properly, I think there is some mismatch between the
source code
and object code used by gdb. I say that because it sometimes steps through code in a way that makes no sense. For example, I
see that a
particular 'if' condition is satified and it goes into the
'if' clause
and then again goes into the 'else' clause that is not expected. Is there any module that needs to be reloaded after building and installing the shared library? I have done a clean make at
all times,
checked timestamps, even rebooted the machine in case some driver related data needs to be reloaded at startup but none of
this has helped.
/sbin/ldconfig refreshes the links for libraries.
I suspect you are debugging optimized code. The optimizer rearranges and deletes instructions. Did you specify -O0 so that no optimization occurs? The other gotcha in the alsa-lib code is that some of the functions are actually macros. They cannot be stepped through. When you hit them in the debugger it is disconcerting.
I did specify -O0 to disable optimizations.
That's weird. Don't have an explanation except yours, that you aren't debugging the code you think you are.