# How dtrace work in ReactiveCocoa?

**URL:** <https://forums.kodeco.com/t/how-dtrace-work-in-reactivecocoa/143668>\
**Category:** Advanced Apple Debugging\
**Created:** [July 6, 2021, 11:31am UTC](https://forums.kodeco.com/t/how-dtrace-work-in-reactivecocoa/143668 "2021-07-06T11:31:07Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![sketchk](https://assets.chunter.kodeco.com/user_avatar/forums.kodeco.com/sketchk/32/102404_2.png) [@sketchk](https://forums.kodeco.com/u/sketchk)\
**Post date:** [July 6, 2021, 11:31am UTC](https://forums.kodeco.com/t/how-dtrace-work-in-reactivecocoa/143668/1 "2021-07-06T11:31:08Z")

</div>

I see some .d file in [ReactiveCocoa 2.5](https://github.com/ReactiveCocoa/ReactiveCocoa/blob/v2.5/ReactiveCocoa/RACSignalProvider.d), like **RACSignalProvider.d** , and the compiler will automatically generate a header file(RACSignalProvider.h) which name is equal to the .d(RACSignalProvider.d) file.

As I know,

1. .d file(RACSignalProvider.d) defines some probes, and we use some script to trigger them.
2. dtrace is work on iOS Simulator, not for iOS Device

so my question is

1. what’s the meaning of the automatically generated header file?(RACSignalProvider.h) , why I need this file?
2. how does .d file work in reactive cocoa, especially on iOS Device? who defines the probe? how to tell the system this probe? how to trigger these probe, and anyone can describe the whole workflow?

---

<div class="post-metadata">

**Author:** ![system](https://s3.amazonaws.com/cdn.raywenderlich.com/community/forum-assets/noun-game-ghost-878668.png) [@system](https://forums.kodeco.com/u/system)\
**Post date:** [December 20, 2021, 3:31am UTC](https://forums.kodeco.com/t/how-dtrace-work-in-reactivecocoa/143668/2 "2021-12-20T03:31:10Z")

</div>

Closed on December 20, 2021, 3:31am UTC

This topic was automatically closed after 166 days. New replies are no longer allowed.
