[lldb-dev] Too many ModuleSP references

[Pavel Labath via lldb-dev]

Thank you for the feedback. I'll look into how to get the expressions
cleared when the breakpoint locations get unresolved. I can also
switch the breakpoints to a weak_ptr if you think that is worthwhile,
but one of the two fixes is enough for me at the moment.

regards,
pavel

On 22 February 2017 at 01:08, Jim Ingham via lldb-dev
<lldb-dev at lists.llvm.org> wrote:
>
>> On Feb 21, 2017, at 4:49 PM, Jim Ingham via lldb-dev <lldb-dev at lists.llvm.org> wrote:
>>
>>
>>> On Feb 21, 2017, at 4:24 PM, Greg Clayton via lldb-dev <lldb-dev at lists.llvm.org> wrote:
>>>
>>>> - StepOverBreakpointTestCase: Have the test not store the breakpoints
>>>> in the test case object. Basically, declare that this is not a bug,
>>>> and it's the users responsibility to clean up necessary objects.
>>>
>>> It would be nice to avoid this.
>>>
>>>>
>>
>> I don't agree with this.  I think trying to force folks using the API from Python to manually clear all stored objects would be really obnoxious.  If anything, we should figure out how to make this accidental failure into an intended failure so we can make sure we don't end up requiring this kind of micro-management.
>
> It's possible you meant "it would be nice to avoid it's being the user's responsibility to clean up necessary objects", in which case sorry for mis-reading but happy we agree...
>
> Jim
>
>
>>
>> Jim
>>
>>
>> _______________________________________________
>> lldb-dev mailing list
>> lldb-dev at lists.llvm.org
>> http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
>
> _______________________________________________
> lldb-dev mailing list
> lldb-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev