the short answer to 'does opmini.c need to be in the creation of the
perldtrace.o' is to apply the following trivial patch, and watch the
build fail.
Frustratingly, this week I've been finding a situation where probes in
op.c don't seem to enable, but the same probe works fine from any other
source file. The op.c ones don't even show up in dtrace -l.
Index: op.c
===================================================================
--- op.c (revision 127)
+++ op.c (working copy)
@@ -3811,6 +3811,7 @@
OP *pegop = newOP(OP_NULL,0);
#endif
+ ENTRY_PROBE("Test", "Probe", 12);
PERL_ARGS_ASSERT_UTILIZE;
if (idop->op_type != OP_CONST)
Andy Armstrong wrote:
> On 17 Feb 2008, at 01:27, Sven Dowideit wrote:
>> Heya Andy,
>>
>> As I have understood it, opmini.c is essentially a copy of op.c, and
>> I've added the load-module probes to op.c, thus forcing this change.
>> I think I also saw this resolve some issues when turning on the
>> dtrace probes while miniperl is running, but that might have been the
>> the 333201 problem I stumbled over.
>
>
> Would be good to get to the bottom of whatever problems you saw I think.
>
_______________________________________________
dtrace-discuss mailing list
[email protected]
