#1495 include talloc log in our debug facility
Closed: Fixed None Opened 7 years ago by pbrezina.

Talloc can detect several types of errors. The most interesting is the ability to detect access after free/double free when the invalid pointer is passed to a talloc function. It logs these violations into a talloc log. More information can be found in the tutorial:

http://talloc.samba.org/talloc/doc/html/libtalloc__debugging.html

We should include this log in our debug facility.


Fields changed

milestone: NEEDS_TRIAGE => Temp milestone
proposed_priority: Undefined => Important
rhbz: => 0

Moving all the features planned for 1.10 release into 1.10 beta.

milestone: Temp milestone => SSSD 1.10 beta

Fields changed

priority: major => minor

Fields changed

priority: minor => major

Fields changed

owner: somebody => mzidek

Fields changed

patch: 0 => 1

Fields changed

status: new => assigned

Fixed in 9e2c64c

design: =>
design_review: => 0
fedora_test_page: =>
resolution: => fixed
status: assigned => closed

For tickets already closed set the field to "Want"

selected: => Want

Metadata Update from @pbrezina:
- Issue assigned to mzidek
- Issue set to the milestone: SSSD 1.10 beta

3 years ago

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

This issue has been cloned to Github and is available here:
- https://github.com/SSSD/sssd/issues/2537

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.

Login to comment on this ticket.

Metadata