From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 124934 invoked by alias); 13 Jun 2018 15:54:10 -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 122811 invoked by uid 48); 13 Jun 2018 15:54:06 -0000 From: "serhei.public at gmail dot com" To: systemtap@sourceware.org Subject: [Bug runtime/23284] New: dmesg should identify the name of the stap script Date: Wed, 13 Jun 2018 15:54:00 -0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: systemtap X-Bugzilla-Component: runtime X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: serhei.public at gmail dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: 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 target_milestone Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-q2/txt/msg00101.txt.bz2 https://sourceware.org/bugzilla/show_bug.cgi?id=3D23284 Bug ID: 23284 Summary: dmesg should identify the name of the stap script Product: systemtap Version: unspecified Status: UNCONFIRMED Severity: normal Priority: P2 Component: runtime Assignee: systemtap at sourceware dot org Reporter: serhei.public at gmail dot com Target Milestone: --- Many systemtap issues can be diagnosed by viewing dmesg output during a testsuite run. Dmesg prints the module name when a stap module is loaded. However, neither systemtap.sum nor systemtap.log record the stap module name for every stap run, so it's not easy to tell which testcase caused a partic= ular warning. This can be fixed by having the runtime print the original name of the scri= pt file to dmesg. The eBPF backend should also do this. --=20 You are receiving this mail because: You are the assignee for the bug.