public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "curzonj at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/18001] New: Using backtrace(), caller(), or callers(n) causes a gcc internal error
Date: Thu, 19 Feb 2015 22:50:00 -0000	[thread overview]
Message-ID: <bug-18001-6586@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=18001

            Bug ID: 18001
           Summary: Using backtrace(), caller(), or callers(n) causes a
                    gcc internal error
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: translator
          Assignee: systemtap at sourceware dot org
          Reporter: curzonj at gmail dot com

Overview: Calling caller() causes a gcc internal error.
Reproduce:

stap -k -v -e 'probe kernel.function("dev_hold") { printf("%s", caller()) }'

Actual Results: GCC internal error during compile.
Expected Results: Compile happens and script runs

I want to use caller, but I tried callers(n) and backtrack() and they caused
the same GCC internal error result.

The compile log and artifacts are here:
https://gist.github.com/curzonj/857090762c52730aa028

root@vagrant-ubuntu-trusty-64:/vagrant# uname -a
Linux vagrant-ubuntu-trusty-64 3.13.0-45-generic #74-Ubuntu SMP Tue Jan 13
19:36:28 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
root@vagrant-ubuntu-trusty-64:/vagrant# dpkg -l | grep linux-image
ii  linux-image-3.13.0-40-generic        3.13.0-40.69                     amd64
       Linux kernel image for version 3.13.0 on 64 bit x86 SMP
ii  linux-image-3.13.0-40-generic-dbgsym 3.13.0-40.69                     amd64
       Linux kernel debug image for version 3.13.0 on 64 bit x86 SMP
ii  linux-image-3.13.0-45-generic        3.13.0-45.74                     amd64
       Linux kernel image for version 3.13.0 on 64 bit x86 SMP
ii  linux-image-3.13.0-45-generic-dbgsym 3.13.0-45.74                     amd64
       Linux kernel debug image for version 3.13.0 on 64 bit x86 SMP
ii  linux-image-virtual                  3.13.0.45.52                     amd64
       This package will always depend on the latest minimal generic kernel
image.
root@vagrant-ubuntu-trusty-64:/vagrant# dpkg -l | grep gcc
ii  gcc                                  4:4.8.2-1ubuntu6                 amd64
       GNU C compiler
ii  gcc-4.8                              4.8.2-19ubuntu1                  amd64
       GNU C compiler
ii  gcc-4.8-base:amd64                   4.8.2-19ubuntu1                  amd64
       GCC, the GNU Compiler Collection (base package)
ii  gcc-4.9-base:amd64                   4.9.1-0ubuntu1                   amd64
       GCC, the GNU Compiler Collection (base package)
ii  libgcc-4.8-dev:amd64                 4.8.2-19ubuntu1                  amd64
       GCC support library (development files)
ii  libgcc1:amd64                        1:4.9.1-0ubuntu1                 amd64
       GCC support library
root@vagrant-ubuntu-trusty-64:/vagrant# dpkg -l | grep systemtap
ii  systemtap                            2.3-1ubuntu1                     amd64
       instrumentation system for Linux
ii  systemtap-common                     2.3-1ubuntu1                     all  
       instrumentation system for Linux (common component)
ii  systemtap-runtime                    2.3-1ubuntu1                     amd64
       instrumentation system for Linux (runtime component)

-- 
You are receiving this mail because:
You are the assignee for the bug.

             reply	other threads:[~2015-02-19 22:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-19 22:50 curzonj at gmail dot com [this message]
2015-02-19 23:08 ` [Bug translator/18001] Using sysname(), " curzonj at gmail dot com
2015-02-19 23:10 ` curzonj at gmail dot com
2015-02-20  3:01 ` curzonj at gmail dot com
2015-02-20 14:30 ` fche at redhat dot com
2015-02-20 17:31 ` curzonj at gmail dot com
2015-02-22  1:51 ` fche at redhat dot com
2020-02-19 21:40 ` fche at redhat 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-18001-6586@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=systemtap@sourceware.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).