public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "peter at peca dot dk" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug uprobes/17623] New: Sometimes probes fail to fire events when running against a multi-threaded application
Date: Wed, 19 Nov 2014 13:51:00 -0000	[thread overview]
Message-ID: <bug-17623-6586@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 17623
           Summary: Sometimes probes fail to fire events when running
                    against a multi-threaded application
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: uprobes
          Assignee: systemtap at sourceware dot org
          Reporter: peter at peca dot dk

Created attachment 7948
  --> https://sourceware.org/bugzilla/attachment.cgi?id=7948&action=edit
The example program that triggers the behavior

I have the following test program (attached as testprog.c)

  #include <pthread.h>
  #include <unistd.h>

  #define WAIT_US 1

  void func1()
  {
  }

  void func2()
  {
  }

  void* thread_main(void *foo)
  {
    for (;;)
    {
      func1();
      usleep(WAIT_US);
      func2();
    }
  }

  int main()
  {
    pthread_t thread;
    pthread_create(&thread, NULL, thread_main, NULL);
    pthread_join(thread, NULL);
    return 0;
  }

I run this program, after compiling it with "gcc -O0 -g -Wall testprog.c -o
testprog -lpthread", and then run this systemtap script (attached as
trace_funcs.stp):

  probe process("testprog").function("func1")
  {
    printf("func1\n")
  }

  probe process("testprog").function("func2")
  {
    printf("func2\n")
  }

Expected output: An endless repetition of "func1\nfunc2\n".

Actual output: Sometimes an endless repetition of "func1\n", and at other times
the expected output.


When I compile with WAIT_US set to 1, it almost always fails. If I set it to 50
about half of the runs fails. If I set it 50000 almost all runs succeed.

If I run "testprog" via the "-c" option to stap, it always works.

If I call thread_main() directly from main() instead of using pthreads, it
always works.


I am experiencing is on a Ubuntu 14.04.1, with the Ubuntu supplies Systemtap of
version 2.3. I have compiled Systemtap version 2.6 from source and got the same
results.

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

             reply	other threads:[~2014-11-19 13:51 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-19 13:51 peter at peca dot dk [this message]
2014-11-19 13:51 ` [Bug uprobes/17623] " peter at peca dot dk
2014-11-19 14:39 ` fche at redhat dot com
2014-11-20  7:49 ` peter at peca dot dk
2014-11-20  7:54 ` peter at peca dot dk
2014-11-20 17:04 ` dsmith at redhat dot com
2014-11-21  7:31 ` peter at peca dot dk
2014-11-21 14:45 ` dsmith at redhat dot com
2014-11-23  7:40 ` peter at peca dot dk
2014-11-23  7:53 ` peter at peca dot dk
2014-11-23 16:49 ` peter at peca dot dk
2014-11-24 15:17 ` dsmith at redhat dot com
2014-11-25 10:24 ` peter at peca dot dk
2021-05-03 22:34 ` 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-17623-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).