|
Revision 2, 1.0 kB
(checked in by jesus, 8 months ago)
|
Apache DTrace crystal-meth... crazy dragons... crazy dragons indeed.
|
| Line | |
|---|
| 1 |
The apr-util-hook-probes patch is a header-only patch to apr-util that |
|---|
| 2 |
introduces optional DTrace probes into hook definitions: |
|---|
| 3 |
hook-entry |
|---|
| 4 |
foreach registration: |
|---|
| 5 |
hook-dispatch-invoke |
|---|
| 6 |
(call) |
|---|
| 7 |
hook-dispatch-complete |
|---|
| 8 |
hook-return |
|---|
| 9 |
|
|---|
| 10 |
Apply this to apr-utils (or patch the installed apr_hooks.h file) |
|---|
| 11 |
|
|---|
| 12 |
|
|---|
| 13 |
The apache-2.2.x-probes patch is all the leg work to add dtrace probes into |
|---|
| 14 |
Apache 2.2.x branch. They will apply to the 2.2.8 distribution |
|---|
| 15 |
successfully (with fuzz). |
|---|
| 16 |
|
|---|
| 17 |
The apache-2.2.8-probes patch fixes up the files in the 2.2.8 distro |
|---|
| 18 |
that aren't in trunk. These are the products of buildconf: |
|---|
| 19 |
configure |
|---|
| 20 |
include/ap_auto_config.h.in |
|---|
| 21 |
|
|---|
| 22 |
Apply both of these (in any order), then add --enable-dtrace to the |
|---|
| 23 |
configure line. |
|---|
| 24 |
|
|---|
| 25 |
It is highly likely that these patches are unclean for non-dtrace use. |
|---|
| 26 |
That means, applying the patch and then not using --enable-dtrace may result |
|---|
| 27 |
in a failure to build. |
|---|
| 28 |
|
|---|
| 29 |
Also, the dtrace -G usage is hard-coded in, so this will not work on Mac OS X |
|---|
| 30 |
without a bit of manual touchup. |
|---|
| 31 |
|
|---|
