#49120 Add poison bytes to objects to determine mis-use
Closed: wontfix 6 years ago Opened 7 years ago by firstyear.

By adding poison bytes to objects we can see if they:

  • Are not called with init properly.
  • Are not called with done() properly.
  • Are being double freed in some cases.

Let me double check... This is for pure debugging purpose and the code won't be included in the release bits, will it? (Like PR_assert?)
Thanks.

Correct! Debug only to find places where we are not using structs properly. Will not affect released code.

Thanks for the confirmation! Then, I think it is free from the milestone. Add the code whenever you need for your testing/debugging.

It'd be interesting to run our reliab/stress test suites with the code!

Metadata Update from @nhosoi:
- Issue assigned to firstyear
- Issue set to the milestone: 1.3.7 backlog

7 years ago

Metadata Update from @firstyear:
- Issue close_status updated to: None
- Issue tagged with: Complex, Security

7 years ago

Metadata Update from @firstyear:
- Issue set to the milestone: 1.4 backlog (was: 1.3.7 backlog)

6 years ago

Really I was doing this for pblock, but with recent changes, it's basically done, so closing.

Metadata Update from @firstyear:
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

6 years ago

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/2179

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: fixed)

3 years ago

Login to comment on this ticket.

Metadata