On Jun 25, 2008, at 12:45 PM, Robert Lor wrote:
> James McIlree wrote:
>> On Oct 27, 2007, at 9:30 AM, Adam Leventhal wrote:
>>
>>
>>> As has been previously stated, it's pretty great to see the
>>> DTrace port to
>>> Mac OS X... if for no other reason than it affords me the
>>> opportunity to
>>> _submit_ bugs rather than being responsible for fixing them ;-)
>>>
>>> If I use a uintptr_t in the prototype for a USDT probe, I get an
>>> error like
>>> this:
>>>
>>
>> This is <rdar://problem/5194316>. The underlying cause is the
>> "D" CTF container. It defines a bunch of default types, which are not
>> considered "base" types. The script / linker magic decides that these
>> types need to be encoded for the script reconstruction. When the
>> script
>> is reconstructed, we don't expect to know about these types, but the
>> "D" CTF container is always defined, and so dtrace believes we're
>> trying to redefine a known type.
>>
>
> Has this bug been fixed in the latest Mac OS X update?
This has not been fixed in 10.5.3.
I can't really comment on when it will be fixed, but in general I
would hazard a guess
that this doesn't rise to the level of impact that would allow it to
be included with a 10.x.x
release. I've been wrong before, YMMV, not recommended for use by
humans, and all
the other usual disclaimers apply.
James M
_______________________________________________
dtrace-discuss mailing list
[email protected]
