Le Wednesday 2 March 2011 12:40:09 Jonas Smedegaard, vous avez écrit : > On Tue, Mar 01, 2011 at 11:39:50PM +0100, Yves-Alexis Perez wrote: > >I'm experiencing segfaults with ghostscript (using it from epstopdf or > >directly on eps files) and would like to provide a meaningful backtrace. > >But as there's no -dbg package that means I have to rebuild it > >completely with -g and -O0. It'd be nice to have the debugging symbols > >somewhere. > > Help much appreciated here. > > I do understand that a -dbg package is essentially a rebuild without > optimizations and without stripping. But I have no expecience in this, > so could use a pointer to some guidelines of whatminimal pieces are > needed to extract and include in that -dbg package and where to put it > (I believe I saw somewhere that there's a trick of putting -dbg libs in > a subdir which makes it extend (not replace) the normal package and get > used if available). > > > - Jonas AFAIK, providing debugging symbols is just a matter of 1) building with "-g -O2" (policy defaults) 2) stripping the symbols without throwing them away (dh_strip has an --dbg- package option therefor). CDBS (which I don't know) has a "Debug package support" entry in its documentation, which seems to indicate that adding a "ghostscript-dbg" package in debian/control is sufficient. /me tries… -- Didier Raboud, proud Debian Developer. CH-1020 Renens odyx@debian.org
Attachment:
signature.asc
Description: This is a digitally signed message part.