examples/pipe/interlock_test.c: fix the uses of uninitialized variables

[yamt]

Summary

examples/pipe/interlock_test.c: fix the uses of uninitialized variables

found by clang warnings.

Impact

Testing

build tested with clang.

[nuttxpr]

[Experimental Bot, please feedback here]

No, this PR does not fully meet the NuttX requirements. While it provides some information, it lacks crucial details.

Here's what's missing:

• Summary:

  • Missing a clear explanation of how the change fixes the uninitialized variables. What was the incorrect behavior, and what is the correct behavior now? Simply saying "fix the uses of uninitialized variables" is not sufficient.
  • Missing issue references if applicable.

• Impact: This section is entirely empty. While many of the impact items might be "NO", it's important to explicitly state that. For example:

  • Impact on user: NO
  • Impact on build: NO (except for potentially fixing compiler warnings)
  • Impact on hardware: NO
  • Impact on documentation: NO
  • Impact on security: Potentially YES (Uninitialized variables can sometimes lead to security vulnerabilities, depending on the context. This needs to be addressed.)
  • Impact on compatibility: NO
  • Anything else to consider: NO

• Testing:

  • While it mentions clang, it lacks specifics. Version of clang, OS, and target architecture are missing.
  • The "Testing logs before change" and "Testing logs after change" sections are empty. These should contain concrete evidence demonstrating the issue before the change and the corrected behavior after the change. Even simple output showing the difference would be helpful.

In short, the PR needs more detail and concrete evidence to demonstrate the problem and the solution. It needs to explicitly address all points in the requirements, even if the answer is "NO."