|
From: | Fischer, Matt |
Subject: | Re: [Libunwind-devel] Crash when unwinding using ARM exidx info |
Date: | Tue, 14 May 2013 22:57:46 +0000 |
Any more thoughts on this? I put together a patch containing the change I mentioned below, so if everybody does agree that it’s the right fix, you should be able to easily merge it in. The patch is located at https://github.com/mattfischer/libunwind, branch “unwind-info-free”. Let me know what you think.
--Matt
From: Fischer, Matt
I just ran it in a loop on a simple backtrace done using DWARF info, and one done using EXIDX info, and neither of them seems to leak in my test. But I’m not sure whether there are other edge cases that would need to be examined.
From:
address@hidden [mailto:address@hidden]
On Behalf Of Arun Sharma
+Ken, Tommi
I think your analysis is right, but I'm not convinced that we're properly freeing memory here. Do you see leaks if you unwind in a loop?
-Arun
CONFIDENTIALITY NOTICE: This email and any attachments are for the sole use of the intended recipient(s) and contain information that may be confidential and/or legally privileged. If you have received this email in error, please notify the sender by reply email and delete the message. Any disclosure, copying, distribution or use of this communication (including attachments) by someone other than the intended recipient is prohibited. Thank you. |
[Prev in Thread] | Current Thread | [Next in Thread] |