This is the mail archive of the systemtap@sourceware.org mailing list for the systemtap project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug dyninst/15049] New: stapdyn mishandling interrupts


http://sourceware.org/bugzilla/show_bug.cgi?id=15049

             Bug #: 15049
           Summary: stapdyn mishandling interrupts
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: dyninst
        AssignedTo: systemtap@sourceware.org
        ReportedBy: dsmith@redhat.com
    Classification: Unclassified


Here's the linux runtime:

====
# stap -e 'probe end { printf("*** exiting ***\n"); exit() }'
^C*** exiting ***
====

Here's the dyninst runtime:

====
stap --runtime=dyninst -e 'probe end { printf("*** exiting ***\n"); exit() }'
*** exiting ***
====

In the above case, stapdyn exits immediately. Let's give stapdyn something to
run so it will hang around:

====
# stap --runtime=dyninst -e 'probe end { printf("*** exiting ***\n"); exit() }'
-c cat
^Cstapdyn: WARNING: Multiple interrupts received, exiting...
*** exiting ***
WARNING: /usr/local/bin/stapdyn exited with status: 1
Pass 5: run failed.  Try again with another '--vp 00001' option.
====

Notice that even though I only interrupted stapdyn once, it complained of
multiple interrupts and exited with a non-zero exit value (which might be
related to bug #15029).

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]