public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "e29253 at jp dot ibm.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/66303] runtime.Caller() returns infinitely deep stack frames on s390x
Date: Thu, 28 May 2015 05:53:00 -0000	[thread overview]
Message-ID: <bug-66303-4-0ZEH8BHgJj@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-66303-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Tatsushi Inagaki <e29253 at jp dot ibm.com> ---
The first invocation of runtime.Caller() with skip==2 successfully detects
kickoff() in callback(), and thus returns ok==true.

The problem is that the succeeding invocations of runtime.Caller() with
skip==3, 4, 5, ... still continue returning ok==true. This is because
callback() returns index==1 and a non-zero pc, which are recognized as valid
information by runtime.Caller() in runitme/go-caller.c. I attached a gdb
session of the second invocation of runtime.Caller() with skip==3.


  parent reply	other threads:[~2015-05-28  5:53 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-27 10:25 [Bug go/66303] New: " e29253 at jp dot ibm.com
2015-05-27 13:39 ` [Bug go/66303] " ian at airs dot com
2015-05-28  5:53 ` e29253 at jp dot ibm.com
2015-05-28  5:53 ` e29253 at jp dot ibm.com [this message]
2015-06-02  9:00 ` vogt at linux dot vnet.ibm.com
2015-06-02  9:41 ` vogt at linux dot vnet.ibm.com
2015-06-02  9:43 ` vogt at linux dot vnet.ibm.com
2015-06-02 11:17 ` vogt at linux dot vnet.ibm.com
2015-06-02 14:04 ` ian at airs dot com
2015-06-03 11:27 ` vogt at linux dot vnet.ibm.com
2015-06-03 13:18 ` vogt at linux dot vnet.ibm.com
2015-06-10  7:00 ` stli at linux dot vnet.ibm.com
2015-07-07 14:21 ` stli at linux dot vnet.ibm.com
2015-08-06  7:06 ` krebbel 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-66303-4-0ZEH8BHgJj@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).