This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Re: g++ 4.7 with g++0x threads & profiling
- From: Pedro Larroy <pedro dot larroy dot lists at gmail dot com>
- To: Folkert van Heusden <folkert dot mobiel at gmail dot com>
- Cc: gcc-help at gcc dot gnu dot org
- Date: Wed, 11 Apr 2012 19:06:09 +0200
- Subject: Re: g++ 4.7 with g++0x threads & profiling
- References: <CAHwprn31+WuW42sdY+SLu9Wxch2YDRS6zLADpiAfrQ2KfB47AQ@mail.gmail.com> <CAHwprn1XUBA09=r_wU2Rj2n5ZJ9pOfRQW5nfZtH3foFCm10hxQ@mail.gmail.com>
Hi
Have you tried oprofile, you will get accurate results under heavy
multithread usage unlike with -pg
Pedro.
On Wed, Apr 11, 2012 at 6:04 PM, Folkert van Heusden
<folkert.mobiel@gmail.com> wrote:
> Hi,
>
> I have a C++ application using the new std::thread functionality.
> At random I see all kinds of crashes, mostly in std::string but also
> in std::map and friends.
> I have profiling (-pg) enabled. It seems that if I disable profiling,
> also the random errors (SIGSEGV) disappear.
> Are there any known issues with profiling, c++0x and gcc version 4.7
> with this? (tried g++ 4.6 as well)
>
>
> Thanks.
>
> Folkert.