From: "ahajkova at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/27933] Use of unitialized functioncall synthetic field in
Date: Wed, 02 Jun 2021 14:19:36 +0000 [thread overview]
Message-ID: <bug-27933-6586-e8jSmGPjml@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27933-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27933
--- Comment #2 from Alexandra Hájková <ahajkova at redhat dot com> ---
valgrind does not complain with the patch anymore
valgrind -q --track-origins=yes stap -v --example helloworld.stp
Pass 1: parsed user script and 501 library scripts using
1382740virt/1108832res/15060shr/1132228data kb, in 95850usr/1340sys/100161real
ms.
Pass 2: analyzed script: 1 probe, 1 function, 0 embeds, 0 globals using
1419292virt/1151492res/15508shr/1168780data kb, in 3060usr/40sys/3116real ms.
Pass 3: translated to C into
"/tmp/stapeR0YmE/stap_404a498339680118b7367fba73a554f3_1083_src.c" using
1419528virt/1155652res/15828shr/1169016data kb, in 290usr/0sys/305real ms.
Pass 4: compiled C into "stap_404a498339680118b7367fba73a554f3_1083.ko" in
30110usr/6930sys/12054real ms.
Pass 5: starting run.
hello world
Pass 5: run completed in 40usr/150sys/507real ms.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2021-06-02 14:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-31 12:21 [Bug translator/27933] New: " mark at klomp dot org
2021-05-31 12:22 ` [Bug translator/27933] " mcermak at redhat dot com
2021-06-02 14:07 ` ahajkova at redhat dot com
2021-06-02 14:19 ` ahajkova at redhat dot com [this message]
2021-06-02 17:02 ` fche 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-27933-6586-e8jSmGPjml@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).