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

[John B Brown]

Dear Folk,

	I'm curious about this "source tree" in which the debug symbols are 
being stored. Is that the tree from which the source and compile data is 
erased once the port is installed by the port command?

	Shalom,

	John B. Brown.
	[jbb at vcn.com]
	358 High Street,
	Buffalo, Wyoming
	82834

"Freedom is not worth having if it does not include
the freedom to make mistakes"  Mahatma Gandhi
"If any question why we died, tell them,
because our fathers lied."  Rudyard Kipling
"A man who does not know the truth is just an idiot
but a man who knows the truth and calls it a lie
is a crook."  Bertolt Brecht
"I wonder whether the world is being run
by smart people who are putting us on
or by imbeciles who really mean it."  Mark Twain

1-307-684-9068

On 7/30/10 7:21 AM, William Knight wrote:
> 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
>>
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
>