Perform the null check right after the memory allocation#885
Perform the null check right after the memory allocation#885lucacome merged 2 commits intoopentracing-contrib:masterfrom
Conversation
WalkthroughThe code change reorders the null pointer check and structure initialization in the Changes
Assessment against linked issues
Suggested labels
📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (1)
⏰ Context from checks skipped due to timeout of 90000ms (20)
🔇 Additional comments (1)
✨ Finishing Touches
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Pull Request Overview
This PR refactors create_opentracing_main_conf to perform a null check immediately after memory allocation, preventing a potential null dereference.
- Moves the default initialization (
*main_conf = opentracing_main_conf_t()) below the null check. - Ensures
nullptris returned ifngx_pcallocfails.
Comments suppressed due to low confidence (1)
opentracing/src/ngx_http_opentracing_module.cpp:255
- [nitpick] Move this comment to just before the assignment on line 257 so it accurately describes the default initialization step and does not precede the null check.
// Default initialize members.
Closes #876
Summary by CodeRabbit