public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fragabr at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/52762] Firefox 11 segfault with gcc 4.7 (-O3 -march=corei7-avx)
Date: Thu, 29 Mar 2012 19:13:00 -0000 [thread overview]
Message-ID: <bug-52762-4-AyhlwwKFK6@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52762-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52762
Dâniel Fraga <fragabr at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |UNCONFIRMED
Resolution|INVALID |
--- Comment #4 from Dâniel Fraga <fragabr at gmail dot com> 2012-03-29 19:02:34 UTC ---
(In reply to comment #3)
> Well, nevermind. I tested some more and discovered the culprit:
> checkCompatibility 1.3 extension... I disabled that and everything is back to
> normal.
>
> Thanks and sorry about the wrong bug report.
Well, I replied too soon... it keeps crashing.
The problem is that it will segfault only when I compile WITHOUT
--enable-debug...
Now it sometimes gives the following error:
ACR (Component): component init
isalloc_validate called with invalid pointer. Crashing...
Segmentation fault
***
I'm unable to get this with --enable-debug, so it's a problem...
I'll try with firefox 12 beta...
next prev parent reply other threads:[~2012-03-29 19:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-29 7:10 [Bug c++/52762] New: " fragabr at gmail dot com
2012-03-29 8:27 ` [Bug c++/52762] " markus at trippelsdorf dot de
2012-03-29 17:41 ` fragabr at gmail dot com
2012-03-29 18:10 ` fragabr at gmail dot com
2012-03-29 19:13 ` fragabr at gmail dot com [this message]
2012-03-29 19:17 ` markus at trippelsdorf dot de
2012-03-29 21:01 ` fragabr at gmail dot com
2012-03-30 19:23 ` andi-gcc at firstfloor dot org
2012-03-30 19:56 ` fragabr at gmail dot com
2012-04-04 15:51 ` jason at gcc dot gnu.org
2013-06-15 0:26 ` paolo.carlini at oracle dot com
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=bug-52762-4-AyhlwwKFK6@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).