public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Iain Buchanan <iaindb@netspace.net.au>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user]  Re: Compile something with debugging information
Date: Wed, 20 Jun 2007 07:48:15 +0800	[thread overview]
Message-ID: <1182296895.11945.2.camel@orpheus> (raw)
In-Reply-To: <5241923.GsZ9TRYdz0@kn.gn.rtr.message-center.info>

On Tue, 2007-06-19 at 13:56 +0200, Alexander Skwar wrote:
> Ingrid wrote:
> 
> > All of a sudden, I'm having problems with the Postfix installation on
> > my server. smtpd dies with a Signal 11.
> > 
> > To debug this, I'd like to build postfix again, but this time portage
> > should not strip the binaries and it should be compiled with debugging
> > information compiled in (ie. with -g).
> > 
> > How would I do that?
> 
> FEATURES="nostrip -ccache keeptemp keepwork test noclean" \

I use 'splitdebug' instead of 'nostrip', because it doesn't leave your
binaries full of debugging info, but puts it into /usr/lib/debug, which
you can then delete at your convenience, without rebuilding.

cya,
-- 
Iain Buchanan <iaindb at netspace dot net dot au>

Subject: Bug#42432: debian-policy: Proposal for CTV for Draft for Proof of
Concept for Draft for Proposal for Proposal for CTV for a CTV to decide on
a proposal for a CTV for the CTV on whether or not we shoud have a CTV on
the /usr/doc to /usr/share/doc transition now, or later.
        -- Ed Lang

-- 
gentoo-user@gentoo.org mailing list



  parent reply	other threads:[~2007-06-20  0:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-19 11:37 [gentoo-user] Compile something with debugging information Alexander Skwar
2007-06-19 11:56 ` [gentoo-user] " Alexander Skwar
2007-06-19 14:32   ` Daniel Pielmeier
2007-06-19 23:48   ` Iain Buchanan [this message]
2007-06-20 10:22   ` Bo Ørsted Andresen
2007-06-19 12:27 ` [gentoo-user] " Alan McKinnon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1182296895.11945.2.camel@orpheus \
    --to=iaindb@netspace.net.au \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox