Date: Tue, 17 Oct 2017 23:29:47 +0200 From: Jan Beich <jbeich@FreeBSD.org> To: Guido Falsi <mad@madpilot.net> Cc: Piotr Kubaj <pkubaj@anongoth.pl>, freebsd-ports@freebsd.org Subject: Re: Debugging ports Message-ID: <y3o9-31kk-wny@FreeBSD.org> In-Reply-To: <fa8be1ce-2408-3e5b-619a-d95accc8631e@madpilot.net> (Guido Falsi's message of "Tue, 17 Oct 2017 23:16:46 %2B0200") References: <20171017160445.GA31080@smtp.iq.pl> <b612c6d0-41f1-4b6a-b424-033fa567d8bf@madpilot.net> <fa8be1ce-2408-3e5b-619a-d95accc8631e@madpilot.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Guido Falsi <mad@madpilot.net> writes: > On 10/17/2017 23:11, Guido Falsi wrote: > >>> >>> Thing is, recompiling with WITH_DEBUG doesn't help (I only get >>> memory addresses in gdb), nor does -DCMAKE_BUILD_TYPE=Debug to >>> CMAKE_ARGS (the port uses CMake). > > Sorry, I clearly did not parse your message correctly. > > Looks strange though, WITH_DEBUG always worked for me... Usually I > compile the whole set in poudriere with WITH_DEBUG, to make sure all > libraries have symbols too. WITH_DEBUG doesn't disable vendor optimizations like -fomit-frame-pointer which may hinder stack unwinding, doesn't enable debug symbols for ports not respecting CFLAGS, often a nop for non-C/C++ ports, etc. Without an example it's hard to guess.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?y3o9-31kk-wny>