From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/18001] Using sysname(), caller(), or callers(n) causes a gcc internal error
Date: Fri, 20 Feb 2015 14:30:00 -0000 [thread overview]
Message-ID: <bug-18001-6586-wWt05p8zRi@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-18001-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=18001
Frank Ch. Eigler <fche at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |fche at redhat dot com
--- Comment #3 from Frank Ch. Eigler <fche at redhat dot com> ---
A gcc internal compiler error is at least a gcc bug (and could also
be a stap bug in terms of C code it generates). I'll add some info to
the error::pass4 man page to help gather data for the gcc guys, but
it'll go something like
stap -k --vp 0004 -p4 .....
cd /var/tmp/stapFOOBAR
edit Makefile to run gcc -E rather than -c
send resulting .i (preprocessed input) and CFLAGS to gcc guys
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2015-02-20 14:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-19 22:50 [Bug translator/18001] New: Using backtrace(), " curzonj at gmail dot com
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 [this message]
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-wWt05p8zRi@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).