How to keep .c files from devel install for debugging?

[William Knight]

Thanks, I am realizing this. At this point I have stopped trying to
use the macports version of certain libs for debugging and am instead
building them manually in a different location. This approach is
working for the most part.

On Thu, Jul 29, 2010 at 11:59 PM, Rainer Müller <raimue at macports.org> wrote:
> On 2010-07-29 21:00 , William Knight wrote:
>> Ok. Just to be more clear, what I'm talking about is stepping in a
>> debugger like gdb through the source code of an application and then
>> into the source code of a library linked with that application. For
>> example, if I created a gtk app and wanted to step into the source
>> code of gtk_init(), then presumably I would need the file gtkmain.c
>> somewhere in the path of the debugger.
>
> First of all you would need the library to be compiled with debug
> symbols. MacPorts does not do this, nor does it offer a generalized way
> to do so.
>
> Also on Mac OS X unlike on other systems debug symbols are not being
> stored in the libraries itself but in extra .dSYM directories. Those
> live in the source tree only next to the object files and are required
> in addition to the source in order to debug the library.
>
> Rainer
>