From: "Mark Knecht" <markknecht@gmail.com>
To: gentoo-amd64@lists.gentoo.org
Subject: [gentoo-amd64] Enabling debug info in Wine?
Date: Fri, 7 Mar 2008 08:09:31 -0800 [thread overview]
Message-ID: <5bdc1c8b0803070809x78898edegd3e2fa8f515582e8@mail.gmail.com> (raw)
Hi all,
What would be a sufficient set of actions for me to take to get
backtrace info from Wine that would be useful to Wine devlopers? Their
Bugzilla folks are are saying, correctly I think, that everything
necessary is stripped out and that the info I'm providing doesn't
help. I don't see anything specific in the Wine flags.
Is this some sort of major effort required where I have to go back
and recompile many things on my system or is there a way to compile
just Wine to give them what they need?
I found this page to read:
http://www.gentoo.org/proj/en/qa/backtraces.xml
I do not understand the nostrip/splitdebug topic. I do not find
either word in man emerge or man portage. Is this a gcc thing?
My current gcc flags look like this:
CFLAGS="-march=k8 -O2 -pipe"
CHOST="x86_64-pc-linux-gnu"
CXXFLAGS="${CFLAGS}"
MAKEOPTS="-j2"
Any comments about whether those are good or not for a
non-developer, desktop user type like me would be appreciated. I don't
mind changing cflags to get these folks what they want.
Thanks,
Mark
--
gentoo-amd64@lists.gentoo.org mailing list
next reply other threads:[~2008-03-07 16:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-07 16:09 Mark Knecht [this message]
2008-03-07 16:47 ` [gentoo-amd64] Re: Enabling debug info in Wine? Mark Knecht
2008-03-07 16:59 ` Chris Brennan
2008-03-07 17:21 ` Mark Knecht
2008-03-07 18:54 ` Duncan
2008-03-07 19:03 ` Mark Knecht
2008-03-07 19:05 ` Mark Knecht
2008-03-08 1:15 ` Duncan
2008-03-08 5:06 ` Duncan
2008-03-08 18:40 ` Mark Knecht
2008-03-09 0:15 ` Duncan
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=5bdc1c8b0803070809x78898edegd3e2fa8f515582e8@mail.gmail.com \
--to=markknecht@gmail.com \
--cc=gentoo-amd64@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