FWIW - since OpenSSL has its own internal allocator, the stack traces recorded by tools like valgrind can be very misleading. I've had times where something like EVP_PKEY_free triggered bad memory usage in completely unrelated code - the only commonality was where in the OpenSSL-managed heap the memory happened to live.
It's a bummer :(
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/xrootd/xrootd","title":"xrootd/xrootd","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/xrootd/xrootd"}},"updates":{"snippets":[{"icon":"PERSON","message":"@bbockelm in #564: FWIW - since OpenSSL has its own internal allocator, the stack traces recorded by tools like `valgrind` can be very misleading. I've had times where something like `EVP_PKEY_free` triggered bad memory usage in completely unrelated code - the only commonality was where in the OpenSSL-managed heap the memory happened to live.\r\n\r\nIt's a bummer :("}],"action":{"name":"View Issue","url":"https://github.com/xrootd/xrootd/issues/564#issuecomment-323730927"}}}
Use REPLY-ALL to reply to list
To unsubscribe from the XROOTD-DEV list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1
