fix: preserve PHP 7.1 ZTS property names

[morrisonlevi]

Description

Fixes a crash that happens during shutdown on PHP 7.1 on ZTS builds. This is happening a lot on the combined tracer+profiler branch, and I wanted it to get reviewed and merged independently since that PR is so big already, and it's not related to the branch.

Common symptom is:

*** Error in `/opt/php/7.1-zts/bin/php-cgi': corrupted double-linked list: 0x000000003662ec20 ***

Which happens in tsrm_shutdown.

Reviewer checklist

• Test coverage seems ok.
• Appropriate labels assigned.

[datadog-prod-us1-3]

 

✨ Unblock PR with BitsAI

⚠️ Warnings

❌ Your PR has failed checks. Please review the issues below and take necessary action before merging.

🚦 12 Pipeline jobs failed

DataDog/apm-reliability/dd-trace-php | check libxml2 version — 🔧 Needs a code fix, caused by this PR

View more details · View in GitLab

DataDog/apm-reliability/dd-trace-php | installer tests — 🔧 Needs a code fix, caused by this PR

View more details · View in GitLab

DataDog/apm-reliability/dd-trace-php | pecl tests: [7.2] — 🔧 Needs a code fix, caused by this PR

View more details · View in GitLab

View all 12 failed jobs.

ℹ️ Info

No other issues found (see more)

🧪 All tests passed
❄️ No new flaky tests detected

🎯 Code Coverage (details)
• Patch Coverage: 100.00%
• Overall Coverage: 54.96% (-0.07%)

Useful? React with 👍 / 👎

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: e1e74cc | Docs | View more details | Give us feedback!}

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-09-10T22:18:32.125999Z	34667bb	Draft marked ready
🔒 Security Review	✅ Completed 2026-09-10T22:19:20.707582Z	34667bb	Draft marked ready

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[pr-commenter]

Benchmarks [ tracer ]

Benchmark execution time: 2026-09-11 03:13:31

Comparing candidate commit e1e74cc in PR branch levi/repro-7.1-zts-uaf-fix with baseline commit fcbed87 in branch master.

Found 1 performance improvements and 4 performance regressions! Performance is the same for 189 metrics, 0 unstable metrics.

Explanation

This is an A/B test comparing a candidate commit's performance against that of a baseline commit. Performance changes are noted in the tables below as:

• 🟩 = significantly better candidate vs. baseline
• 🟥 = significantly worse candidate vs. baseline

We compute a confidence interval (CI) over the relative difference of means between metrics from the candidate and baseline commits, considering the baseline as the reference.

If the CI is entirely outside the configured SIGNIFICANT_IMPACT_THRESHOLD (or the deprecated UNCONFIDENCE_THRESHOLD), the change is considered significant.

Feel free to reach out to #apm-benchmarking-platform on Slack if you have any questions.

More details about the CI and significant changes

You can imagine this CI as a range of values that is likely to contain the true difference of means between the candidate and baseline commits.

CIs of the difference of means are often centered around 0%, because often changes are not that big:

---------------------------------(------|---^--------)-------------------------------->
                              -0.6%    0%  0.3%     +1.2%
                                 |          |        |
         lower bound of the CI --'          |        |
sample mean (center of the CI) -------------'        |
         upper bound of the CI ----------------------'

As described above, a change is considered significant if the CI is entirely outside the configured SIGNIFICANT_IMPACT_THRESHOLD (or the deprecated UNCONFIDENCE_THRESHOLD).

For instance, for an execution time metric, this confidence interval indicates a significantly worse performance:

----------------------------------------|---------|---(---------^---------)---------->
                                       0%        1%  1.3%      2.2%      3.1%
                                                  |   |         |         |
       significant impact threshold --------------'   |         |         |
                      lower bound of CI --------------'         |         |
       sample mean (center of the CI) --------------------------'         |
                      upper bound of CI ----------------------------------'

scenario:SamplingRuleMatchingBench/benchRegexMatching1

• 🟥 execution_time [+57.682ns; +119.718ns] or [+3.920%; +8.136%]

scenario:SamplingRuleMatchingBench/benchRegexMatching2

• 🟥 execution_time [+60.252ns; +141.948ns] or [+4.082%; +9.616%]

scenario:SamplingRuleMatchingBench/benchRegexMatching2-opcache

• 🟩 execution_time [-16.921µs; -16.713µs] or [-91.380%; -90.255%]

scenario:SamplingRuleMatchingBench/benchRegexMatching3

• 🟥 execution_time [+94.289ns; +164.111ns] or [+6.303%; +10.970%]

scenario:SamplingRuleMatchingBench/benchRegexMatching4

• 🟥 execution_time [+55.055ns; +132.545ns] or [+3.715%; +8.944%]