Because of following reasons:
* WPP is only run on free not in debug. * WPP should explicit to be operate. that means when we need it, it will not be. * Using WPP is more complicate. You need to take the binaries and format it. Afterward filtering of specific data is complicated. * Using internal data allows us to right a debugger extension and filter the data easily From: [email protected] [mailto:[email protected]] On Behalf Of Fab Tillier Sent: Tuesday, December 07, 2010 1:48 AM To: Irena Gannon; '[email protected]' Subject: Re: [ofw] Reference count debugging mechanism proposal Why not just use WPP/ETW tracing for this, rather than re-implement the logging? The WPP/ETW tracing has the advantage that the logs could be gathered in one place and analyzed in another. You can trace all the same information as you propose. -Fab From: [email protected] [mailto:[email protected]] On Behalf Of Irena Gannon Sent: Monday, November 29, 2010 8:46 AM To: '[email protected]' Subject: [ofw] Reference count debugging mechanism proposal Hello, Please review the attached proposal for adding debugging information to the reference count mechanism. Thank you, Irena
_______________________________________________ ofw mailing list [email protected] http://lists.openfabrics.org/cgi-bin/mailman/listinfo/ofw
