Hi list, I''m currently trying to build a sdt provider into an application. Before we moved our code into the code itself, parts of the provider were provided by an extension loaded by the program. As a result the function-entry probe already exists. Now if I compile my program with my probes which reimplement function-entry (so provider name and probe name match), I get the following error: Assertion failed: strcmp(pvp->pv_desc.dtvd_name, pdp->dtpd_provider) =0, file ../common/dt_provider.c, line 246 Do you know how dtrace get''s it''s information about the old provider and how I can remove it? In this case were are talking about the dtrace extension of php distributed with OpenSolaris. David
> I''m currently trying to build a sdt provider into an application. Before > we moved our code into the code itself, parts of the provider were > provided by an extension loaded by the program. As a result the > function-entry probe already exists. Now if I compile my program with my > probes which reimplement function-entry (so provider name and probe name > match), I get the following error: > > Assertion failed: strcmp(pvp->pv_desc.dtvd_name, pdp->dtpd_provider) => 0, file ../common/dt_provider.c, line 246 > > Do you know how dtrace get''s it''s information about the old provider and > how I can remove it? > > In this case were are talking about the dtrace extension of php > distributed with OpenSolaris.Hey David, Sorry about that. Please file a bug if you haven''t already. Adam -- Adam Leventhal, Fishworks http://blogs.sun.com/ahl
Possibly Parallel Threads
- 6370454 dtrace should support USDT probes in static functions
- Two submitted packages
- bottom legends in ggplot2 ?
- Is binary firmware still necessary for GTX660 card (NVE0 family) in order to use DRM and/or VDPAU video acceleration?
- [PATCH] vhost_net: use packet weight for rx handler, too