On Jun 24, 6:12pm, m...@3am-software.com (Matt Thomas) wrote:
-- Subject: Re: DTrace syscall provider - please test/comment
|
| On Jun 24, 2013, at 6:01 PM, Christos Zoulas chris...@astron.com wrote:
|
| Can't this be done as an addition/enhancement to the trace_enter()/
| trace_exit
On Jun 25, 2013, at 5:25 AM, chris...@zoulas.com (Christos Zoulas) wrote:
On Jun 24, 6:12pm, m...@3am-software.com (Matt Thomas) wrote:
-- Subject: Re: DTrace syscall provider - please test/comment
|
| On Jun 24, 2013, at 6:01 PM, Christos Zoulas chris...@astron.com wrote:
|
| Can't
On Jun 25, 9:32am, m...@3am-software.com (Matt Thomas) wrote:
-- Subject: Re: DTrace syscall provider - please test/comment
|
| On Jun 25, 2013, at 5:25 AM, chris...@zoulas.com (Christos Zoulas) wrote:
|
| On Jun 24, 6:12pm, m...@3am-software.com (Matt Thomas) wrote:
| -- Subject: Re
On Tue, Jun 25, 2013 at 01:06:58PM -0400, Christos Zoulas wrote:
I am trying to balance that against adding of two more conditionals per
syscall per architecture and touching dozens of source files adding the
same code in each one. Perhaps the syscall_plain/syscall_fancy idea
One solution
On Jun 25, 2013, at 10:19 AM, Jeff Rizzo r...@tastylime.net wrote:
On 6/25/13 10:06 AM, Christos Zoulas wrote:
On Jun 25, 9:32am, m...@3am-software.com (Matt Thomas) wrote:
-- Subject: Re: DTrace syscall provider - please test/comment
|
| On Jun 25, 2013, at 5:25 AM, chris...@zoulas.com
