Date: Sat, 22 Dec 2012 10:08:05 -0800 From: Alfred Perlstein <bright@mu.org> To: Ed Maste <emaste@freebsd.org> Cc: freebsd-hackers@freebsd.org, Rui Paulo <rpaulo@freebsd.org> Subject: Re: malloc+utrace, tracking memory leaks in a running program. Message-ID: <50D5F705.8020303@mu.org> In-Reply-To: <CAPyFy2BNqvSENz7sfOHMP9d%2BgqJ0rbvmG4QA3mEO2VLT_7ruoQ@mail.gmail.com> References: <50D52B10.1060205@mu.org> <CAPyFy2BNqvSENz7sfOHMP9d%2BgqJ0rbvmG4QA3mEO2VLT_7ruoQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 12/22/12 8:56 AM, Ed Maste wrote: > On 21 December 2012 22:37, Alfred Perlstein <bright@mu.org> wrote: > >> Is it time to start installing with some form of debug symbols? This would >> help us also with dtrace. > I just posted a patch to add a knob to build and install standalone > debug files. My intent is that we will build releases with this > enabled, and add a base-dbg.txz distribution that contains the debug > data for the base system, so that one can install it along with > everything else, or add it later on when needed. > > We could perhaps teach dtrace to read its data from standalone .ctf > files, or have it read DWARF directly and use the same debug files. > Thank you. Added CC'd Rui Paulo. Rui, do you think it's easy to get dtrace to honor these conventions? -Alfred
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?50D5F705.8020303>