From: David Jacobs <jda@melexis.com>
To: gcc-help@gcc.gnu.org
Subject: program crash after using -pg option?
Date: Wed, 03 Mar 2010 13:26:00 -0000 [thread overview]
Message-ID: <4B8E639E.8060502@melexis.com> (raw)
Hello,
I'm having some problems using the -pg option to gather profiling data.
It's the first time I use this option, so I might be overlooking
something obvious. :-)
When I add the -pg option to both compiler and linker I get the
following errors while executing my program:
(compilation and linking is fine)
--------------------
264 [main] TempLnrTransform 3568 _cygtls::handle_exceptions: Exception:
STATUS_ACCESS_VIOLATION
6953 [main] TempLnrTransform 3568 open_stackdumpfile: Dumping stack
trace to TempLnrTransform.exe.stackdump
947884 [main] TempLnrTransform 3568 _cygtls::handle_exceptions:
Exception: STATUS_ACCESS_VIOLATION
981347 [main] TempLnrTransform 3568 _cygtls::handle_exceptions: Error
while dumping state (probably corrupted stack)/
--------------------
/It seems the added functions of mcount are causing some problems?
The program runs fine without the -pg option.
Any idea where to look for?
Cheers,
David
next reply other threads:[~2010-03-03 13:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-03 13:26 David Jacobs [this message]
2010-03-03 14:50 ` Tim Prince
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=4B8E639E.8060502@melexis.com \
--to=jda@melexis.com \
--cc=gcc-help@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).