But what about the case Vedant mentioned?
>Otherwise, when a std::shared_ptr is destroyed, the destructor for
> the derived TraceIntelPT instance won't run.
Or is C++ smart enough to pick the destructor from TraceIntelPT class in this
case?
On 9/30/20, 5:56 AM, "Pavel Labath" wrote:
On 30/09/2020 20:25, Walter Erquinigo wrote:
> But what about the case Vedant mentioned?
>
>>Otherwise, when a std::shared_ptr is destroyed, the destructor for
>> the derived TraceIntelPT instance won't run.
>
> Or is C++ smart enough to pick the destructor from TraceIntelPT class in this
>
On 29/09/2020 22:09, Walter Erquinigo via lldb-commits wrote:
> The destructor must be defined in the implementation class so that it
> can be called
That doesn't sound right. Each class automatically gets a destructor if
it does not declare one itself. "~Foo() override = default" is
completely eq
Author: Walter Erquinigo
Date: 2020-09-29T13:09:52-07:00
New Revision: 92e1ebeaa1fe0e5461327d071c55167733834e60
URL:
https://github.com/llvm/llvm-project/commit/92e1ebeaa1fe0e5461327d071c55167733834e60
DIFF:
https://github.com/llvm/llvm-project/commit/92e1ebeaa1fe0e5461327d071c55167733834e60.di
