From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19239 invoked by alias); 12 Nov 2014 01:21:06 -0000 Mailing-List: contact systemtap-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: systemtap-owner@sourceware.org Received: (qmail 19220 invoked by uid 48); 12 Nov 2014 01:21:03 -0000 From: "fche at redhat dot com" To: systemtap@sourceware.org Subject: [Bug translator/17587] New: too sensitive to duplicate globals across tapset files Date: Wed, 12 Nov 2014 01:21:00 -0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: systemtap X-Bugzilla-Component: translator X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: fche at redhat dot com X-Bugzilla-Status: NEW X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: systemtap at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2014-q4/txt/msg00143.txt.bz2 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.