This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug translator/17587] New: too sensitive to duplicate globals across tapset files
- From: "fche at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sourceware dot org
- Date: Wed, 12 Nov 2014 01:21:01 +0000
- Subject: [Bug translator/17587] New: too sensitive to duplicate globals across tapset files
- Auto-submitted: auto-generated
https://sourceware.org/bugzilla/show_bug.cgi?id=17587
Bug ID: 17587
Summary: too sensitive to duplicate globals across tapset files
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: translator
Assignee: systemtap at sourceware dot org
Reporter: fche at redhat dot com
It has been reported that the glib-supplied tapset files
{32,64}-gobject.stp are near-duplicates of one another,
specifically they contain identical
global gtypes
If an end-user script causes both tapset files to be
processed, this results in
semantic error: conflicting global variables: identifier 'gtypes' at
/usr/share/systemtap/tapset/64-gobject.stp:1:8
source: global gtypes
[...]
In this case, this error need not even be one: a single
global variable can be shared between the tapset files.
(If there were a type incompatibility, that would be
detected separately.)
Before we jump in with a big module/namespace system,
let's change that error to a warning, so this case is
handled similarly to the existing "cross-file global variable"
situation. (Indeed, the original reported script
necessarily triggers both sets of diagnostics.)
--
You are receiving this mail because:
You are the assignee for the bug.