public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "michael.hudson at canonical dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/64001] gccgo: crash on stack splitting
Date: Thu, 04 Dec 2014 00:27:00 -0000	[thread overview]
Message-ID: <bug-64001-4-tXkEJYvZXU@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64001-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64001

--- Comment #4 from Michael Hudson-Doyle <michael.hudson at canonical dot com> ---
Well, it seems to report that __morestack_segments &
__morestack_current_segment are always NULL for all threads.  I don't
understand the morestack code perfectly, but this seems a bit unlikely to
actually be the case.

"GNU gdb (Ubuntu 7.8-1ubuntu4) 7.8.0.20141001-cvs" seems like it should be new
enough?


  parent reply	other threads:[~2014-12-04  0:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-20 16:56 [Bug go/64001] New: " michael.hudson at canonical dot com
2014-12-03  2:23 ` [Bug go/64001] " michael.hudson at canonical dot com
2014-12-03  2:48 ` michael.hudson at canonical dot com
2014-12-03  4:22 ` ian at airs dot com
2014-12-04  0:27 ` michael.hudson at canonical dot com [this message]
2015-01-31  2:18 ` ian at airs dot com
2015-02-01 22:05 ` michael.hudson at canonical dot com
2015-02-02 16:19 ` ian at airs 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-64001-4-tXkEJYvZXU@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).