Author loewis
Recipients Robert.Buchholz, bkabrda, christian.heimes, dmalcolm, eric.araujo, fche, jcea, loewis, mjw, pitrou, scox
Date 2014-05-19.20:49:57
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1400532598.05.0.990217622535.issue14776@psf.upfronthosting.co.za>
In-reply-to
Content
I still wish there was a patch that combined both dtrace and systemtap support, und used as much code sharing between them as feasible. I'd be +1 on such a patch, and -0 on two separate patches that achieve the same functionality, but on different code paths.

For example, the systemtap version has a helper function get_frame_marker_info that covers more cases than the dtrace version; OTOH, the dtrace version has more trace points.

If consensus on functionality is not easily achieved, I propose to have the intersection on functionality first, i.e. only use the function-entry/exit trace points even in the dtrace version. Or else you agree on what trace points both systems ought to provide.
History
Date User Action Args
2014-05-19 20:49:58loewissetrecipients: + loewis, jcea, pitrou, christian.heimes, eric.araujo, dmalcolm, mjw, Robert.Buchholz, fche, scox, bkabrda
2014-05-19 20:49:58loewissetmessageid: <1400532598.05.0.990217622535.issue14776@psf.upfronthosting.co.za>
2014-05-19 20:49:58loewislinkissue14776 messages
2014-05-19 20:49:57loewiscreate