public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
* [Bug runtime/10665] New: backtrace() is too slow
@ 2009-09-18 21:39 wcohen at redhat dot com
  2009-09-18 21:42 ` [Bug runtime/10665] " wcohen at redhat dot com
                   ` (7 more replies)
  0 siblings, 8 replies; 9+ messages in thread
From: wcohen at redhat dot com @ 2009-09-18 21:39 UTC (permalink / raw)
  To: systemtap

Trying to use backtrace() for bz6960 so that the code is portable between
different kernels. However, the backtrace() function is so slow that the script
skips probe handlers way too often and exits the script.

Looking through the code for the backtrace() it flushes the buffer, uses the 
normal print to buffer and then copy things from the buffer. That has some overhead.

-- 
           Summary: backtrace() is too slow
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: runtime
        AssignedTo: systemtap at sources dot redhat dot com
        ReportedBy: wcohen at redhat dot com
OtherBugsDependingO 6960
             nThis:


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

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

^ permalink raw reply	[flat|nested] 9+ messages in thread

end of thread, other threads:[~2010-04-17 14:56 UTC | newest]

Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2009-09-18 21:39 [Bug runtime/10665] New: backtrace() is too slow wcohen at redhat dot com
2009-09-18 21:42 ` [Bug runtime/10665] " wcohen at redhat dot com
2009-09-18 21:56 ` wcohen at redhat dot com
2009-09-18 21:59 ` fche at redhat dot com
2009-09-18 23:42 ` wcohen at redhat dot com
2009-10-28 13:12 ` mjw at redhat dot com
2010-01-18 20:17 ` fche at redhat dot com
2010-01-19 10:54 ` alexl at redhat dot com
2010-04-17 15:25 ` fche at redhat dot com

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).