This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug translator/18001] New: Using backtrace(), caller(), or callers(n) causes a gcc internal error
- From: "curzonj at gmail dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sourceware dot org
- Date: Thu, 19 Feb 2015 22:50:38 +0000
- Subject: [Bug translator/18001] New: Using backtrace(), caller(), or callers(n) causes a gcc internal error
- Auto-submitted: auto-generated
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.
- Follow-Ups:
- [Bug translator/18001] Using sysname(), caller(), or callers(n) causes a gcc internal error
- From: curzonj at gmail dot com
- [Bug translator/18001] Using sysname(), caller(), or callers(n) causes a gcc internal error
- From: curzonj at gmail dot com
- [Bug translator/18001] Using sysname(), caller(), or callers(n) causes a gcc internal error
- From: curzonj at gmail dot com
- [Bug translator/18001] Using sysname(), caller(), or callers(n) causes a gcc internal error
- From: fche at redhat dot com
- [Bug translator/18001] Using sysname(), caller(), or callers(n) causes a gcc internal error
- From: curzonj at gmail dot com
- [Bug translator/18001] Using sysname(), caller(), or callers(n) causes a gcc internal error
- From: fche at redhat dot com