From: Tim Prince <n8tm@aol.com>
To: gcc-help@gcc.gnu.org
Subject: Re: program crash after using -pg option?
Date: Wed, 03 Mar 2010 14:50:00 -0000 [thread overview]
Message-ID: <4B8E73E8.5010308@aol.com> (raw)
In-Reply-To: <4B8E639E.8060502@melexis.com>
On 3/3/2010 5:26 AM, David Jacobs wrote:
>
> 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.
>
You're getting well outside the area which is taken care of by gcc.
Threading and profiling libraries aren't part of gcc. Threading is flaky
enough in cygwin that there's a good chance the mcount isn't thread safe
or some other problem comes up which hasn't been tested. While the
situation may have improved, in the past I've submitted bugzillas about
how profiling cases in the gcc testsuite were set up with specific
options for various targets, giving the wrong options for cygwin, so
that the test could not give a useful result, and been told that
testsuite would not be corrected for this. I don't think there are
tests there which combine -pg and threads, in case that is what you are
doing. If it were possible to interest someone in this, you would need
to submit a small reproducer on a cygwin specific list.
prev parent reply other threads:[~2010-03-03 14:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-03 13:26 David Jacobs
2010-03-03 14:50 ` Tim Prince [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=4B8E73E8.5010308@aol.com \
--to=n8tm@aol.com \
--cc=gcc-help@gcc.gnu.org \
--cc=tprince@nospamcomputer.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).