public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "mcermak at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/20281] probe process("")  kills stap with SIGABRT
Date: Fri, 24 Jun 2016 13:11:00 -0000	[thread overview]
Message-ID: <bug-20281-6586-JTq1ygkdmX@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-20281-6586@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=20281

--- Comment #2 from Martin Cermak <mcermak at redhat dot com> ---
Created attachment 9357
  --> https://sourceware.org/bugzilla/attachment.cgi?id=9357&action=edit
proposed patch

Another, maybe a smarter way to solve this.  Attached patch would produce
following error message:

=======
work #  /opt/mystap/bin/stap -p4 --poison-cache -ve 'probe process("").syscall
{ println("hey") }' -c /bin/ls
Pass 1: parsed user script and 0 library scripts using
212104virt/16728res/8076shr/8432data kb, in 0usr/0sys/0real ms.
semantic error: resolution failed in 

semantic error: while resolving probe point: identifier 'process' at
<input>:1:7
        source: probe process("").syscall { println("hey") }
                      ^

semantic error: empty module

Pass 2: analyzed script: 0 probes, 0 functions, 0 embeds, 0 globals using
212104virt/16728res/8076shr/8432data kb, in 0usr/0sys/0real ms.
Pass 2: analysis failed.  [man error::pass2]
work #
=======

-- 
You are receiving this mail because:
You are the assignee for the bug.

  parent reply	other threads:[~2016-06-24 13:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-21  9:58 [Bug translator/20281] New: " mcermak at redhat dot com
2016-06-21 12:52 ` [Bug translator/20281] " mcermak at redhat dot com
2016-06-24 13:11 ` mcermak at redhat dot com [this message]
2016-06-28  4:24 ` mcermak at redhat dot com
2016-06-28 14:36 ` mcermak 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-20281-6586-JTq1ygkdmX@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).