From: "rgoldber at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/30570] New: Type inference for elided try-catch block has unresolved error variable type
Date: Tue, 20 Jun 2023 19:05:18 +0000 [thread overview]
Message-ID: <bug-30570-6586@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=30570
Bug ID: 30570
Summary: Type inference for elided try-catch block has
unresolved error variable type
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: translator
Assignee: systemtap at sourceware dot org
Reporter: rgoldber at redhat dot com
Target Milestone: ---
$ stap -p2 -e 'probe oneshot{try { } catch (e) { printf("%d", e) } }'
semantic error: unresolved type : identifier 'e' at <input>:1:30
source: probe oneshot{try { } catch (e) { printf("%d", e) } }
^
Pass 2: analysis failed. [man error::pass2]
The type of e is unknown, but it should be resolved as a string
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2023-06-20 19:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-20 19:05 rgoldber at redhat dot com [this message]
2023-06-29 13:22 ` [Bug translator/30570] " rgoldber 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-30570-6586@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).