From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug translator/10000] buildok/seventeen.stp fails "integer constant is too large"
Date: Wed, 25 Mar 2009 09:11:00 -0000 [thread overview]
Message-ID: <20090325015914.11710.qmail@sourceware.org> (raw)
In-Reply-To: <20090325011529.10000.jistone@redhat.com>
------- Additional Comments From fche at redhat dot com 2009-03-25 01:59 -------
The problem is another instance of the module_bias/_stext-related
address calculations. Data global vars are not getting consistently
processed.
This is not a new problem. :-( dejazilla shows lots of failures.
This is not a consistent problem. Some combinations of
systemtap / elfutils / kernel versions work, some don't.
--
http://sourceware.org/bugzilla/show_bug.cgi?id=10000
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next prev parent reply other threads:[~2009-03-25 1:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-25 2:01 [Bug translator/10000] New: " jistone at redhat dot com
2009-03-25 9:11 ` fche at redhat dot com [this message]
2009-03-25 13:21 ` [Bug translator/10000] " roland at gnu dot org
2009-03-25 14:27 ` wenji dot huang at oracle dot com
2009-03-25 17:55 ` 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=20090325015914.11710.qmail@sourceware.org \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sources.redhat.com \
/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).