public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ian at airs dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/50166] ICE in go1: SEGV on Solaris 10/x86
Date: Wed, 24 Aug 2011 18:08:00 -0000	[thread overview]
Message-ID: <bug-50166-4-2xOR2ujfM2@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-50166-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50166

--- Comment #1 from Ian Lance Taylor <ian at airs dot com> 2011-08-24 17:59:14 UTC ---
I haven't been able to recreate this crash yet.  According to the backtrace the
crash occurs the very first time a value is added to
Integer_type::named_integer_types, which is a std::map.  The backtrace seems to
show that the code is trying to decrement a variable set to end(), which
crashes because the map is empty.  I don't know why this is happening.  With
the information I have so far it does not seem to be Go related.


  reply	other threads:[~2011-08-24 18:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-23 15:50 [Bug go/50166] New: " ro at gcc dot gnu.org
2011-08-24 18:08 ` ian at airs dot com [this message]
2011-08-25 13:57 ` [Bug go/50166] " ro at CeBiTec dot Uni-Bielefeld.DE
2011-08-26 14:36 ` [Bug target/50166] .init_array/.fini_array support doesn't work on Solaris ro at gcc dot gnu.org
2011-08-26 16:02 ` ro at gcc dot gnu.org
2012-02-17 16:04 ` ian at airs dot com
2012-02-17 17:55 ` ro at CeBiTec dot Uni-Bielefeld.DE
2012-02-22 22:05 ` jingyu at gcc dot gnu.org
2012-02-22 22:29 ` jingyu at gcc dot gnu.org
2012-03-22  8:35 ` rguenth at gcc dot gnu.org
2012-07-02 14:08 ` rguenth at gcc dot gnu.org

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-50166-4-2xOR2ujfM2@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).