jiridanek opened a new pull request #1135: URL: https://github.com/apache/qpid-dispatch/pull/1135
This is an alternative approach compared to #1118. From looking at the (many) errors it produces, it is just as well able to reveal issues * https://issues.apache.org/jira/browse/DISPATCH-2045 qd_hash_internal_remove_item writes to freed (pooled) memory on router shutdown * https://issues.apache.org/jira/browse/DISPATCH-2056 AddressSanitizer: use-after-poison in qdr_connection_set_context during system_tests_http2 It is able to also find the following, that's why I had to put the no_sanitize attribute there * https://issues.apache.org/jira/browse/DISPATCH-2060 use-after free in qd_alloc_deref_safe_ptr if a pool item has been freed due to global_free_list size limit The stacktraces produced from malloc/free are much nicer than the ones from poisoning. The poisoning report is bare-bones, whereas with malloc/free 1. there is a stacktrace for the free call 2. the allocation stack trace is related to this particular use of the pool item, not simply the trace from when the item was first allocated if now it is being reused -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
