public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "zhuizhuhaomeng at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug server/26247] New: stap crash after Eliding side-effect-free expression
Date: Thu, 16 Jul 2020 02:32:37 +0000	[thread overview]
Message-ID: <bug-26247-6586@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 26247
           Summary: stap crash after Eliding side-effect-free expression
           Product: systemtap
           Version: unspecified
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: server
          Assignee: systemtap at sourceware dot org
          Reporter: zhuizhuhaomeng at gmail dot com
  Target Milestone: ---

c code compile with cmd:  cc -g -O0 -Wall -std=gnu99 test.c

#cat test.c
typedef struct foo {
    int a;
} foo_t;

foo_t *v[1];

int main(void) {
    return 0;
}


stap code here:
# cat test.stp

function func_test()
{
    (var2_p = @vma(0x601038, "/tmp/a.out"));
}

probe process("/tmp/a.out").statement(0x4004f7) {
    func_test();
}


run with the following cmd
#stap -d ./a.out -c ./a.out test.stp

WARNING: address 0x4004f7 does not match the beginning of a statement (try
0x4004f6)
WARNING: Eliding assignment to 'var2_p': operator '=' at test.stp:3:14
 source:            (var2_p = @vma(0x601038, "/tmp/a.out"));
                            ^
WARNING: Eliding side-effect-free expression : identifier 'func_test' at :7:6
 source:            func_test();
                    ^
run_core.sh: line 2:  8767 Segmentation fault      (core dumped) stap -d
./a.out -c ./a.out test.stp

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

             reply	other threads:[~2020-07-16  2:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-16  2:32 zhuizhuhaomeng at gmail dot com [this message]
2020-07-16  2:50 ` [Bug server/26247] " zhuizhuhaomeng at gmail dot com
2020-07-16 12:04 ` 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-26247-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).