From: John Myers <electronerd@monolith3d.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Best way to build a debugging binary
Date: Mon, 5 Sep 2005 15:19:08 -0700 [thread overview]
Message-ID: <200509051519.09319.electronerd@monolith3d.com> (raw)
In-Reply-To: <1125959532.27355.3.camel@malory>
[-- Attachment #1: Type: text/plain, Size: 715 bytes --]
On Monday 05 September 2005 15:32, Alex Bennee wrote:
> Hi,
>
> I keep getting crashes when exiting evolution so I thought I'd have a go
> at generating a decent debugging build so I can submit a bug report.
>
> I thought the best thing to do would be re-emerge evolution with
> debugging enabled:
>
> CFLAGS="-g3 -O0" USE="debug" emerge -v evolution
>
> However this doesn't seem to be having the desired effect. For one
> emerge cleans up the build so there is no reference source tree. The
> other is the debugging symbols don't seem to be fully there. e.g:
>
[snip]
> Whats the proper "gentoo" way to build something with symbols for
> getting decent backtraces from?
>
try FEATURES="nostrip keepwork" as well
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2005-09-06 5:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-05 22:32 [gentoo-user] Best way to build a debugging binary Alex Bennee
2005-09-05 22:19 ` John Myers [this message]
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=200509051519.09319.electronerd@monolith3d.com \
--to=electronerd@monolith3d.com \
--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