Re: [lldb-dev] Too many ModuleSP references
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-devwrote: > >> On Feb 21, 2017, at 4:49 PM, Jim Ingham via lldb-dev >> wrote: >> >> >>> On Feb 21, 2017, at 4:24 PM, Greg Clayton via lldb-dev >>> 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@lists.llvm.org >> http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev > > ___ > lldb-dev mailing list > lldb-dev@lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev ___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
[lldb-dev] [4.0.0 Release] Current status
According to the schedule on llvm.org, we should have tagged 'final' yesterday, so the release is now officially a little behind schedule. There are currently seven blockers (llvm.org/pr31622). Several of them have patches. If you can help reviewing them, please do so. - PR30256: Assert in llvm::ReassociatePass::OptimizeAdd There's a patch in progress that looks promising. - PR30284: Assertion `!B->isCollapsed() && "Cannot merge from collapsed There's a patch (D30242) but it needs more attention. - PR31181: wrong code with "opt [..] -correlated-propagation [..] -indvars" The problem seems somewhat understood but there is no patch. - PR31729: GVNHoist illegally hoists div instruction There is a patch (D29092) that looks promising but currently stuck(?). - PR31847: After r288115: Assertion failed: (isLoopInvariant(Operands[i], L) There is a patch (D29641) but no recent progress. - PR31863: Clang can't read back a PCH just produced There is a patch (D29753) but it's stuck. - PR31864: incorrect _GCC_ATOMIC_LLONG_LOCK_FREE values on i386-freebsd There is a patch (D29542) but it lacks active review. There are also a few patches in my merge queue waiting for approvals. Thanks, Hans ___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
[lldb-dev] problem question, LLDB: process launch failed: Lost debug server connection
Hello. I am Lee. I have trouble to run lldb. My system is Ubutu 16.10-server & downloaded lldb version 3.8.1 via apt-get install. I wand just local debugging. But err message is like below. tt@ttt:~/trunk$ lldb /system/bin/cwm Traceback (most recent call last): File "", line 1, in ImportError: No module named lldb.embedded_interpreter (lldb) target create "/system/bin/cwm" Current executable set to '/system/bin/cwm' (i386). (lldb) r error: process launch failed: Lost debug server connection (lldb) Plz answer about this problem Thank you. --- 이 이메일은 Avast 안티바이러스 소프트웨어로 바이러스 검사를 완료했습니다. https://www.avast.com/antivirus ___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
[lldb-dev] problem question, LLDB: process launch failed: Lost debug server connection
Hello. I am Lee. I have trouble to run lldb. My system is Ubutu 16.10-server & downloaded lldb version 3.8.1 via apt-get install. I wand just local debugging. But err message is like below. tt@ttt:~/trunk$ lldb /system/bin/cwm Traceback (most recent call last): File "", line 1, in ImportError: No module named lldb.embedded_interpreter (lldb) target create "/system/bin/cwm" Current executable set to '/system/bin/cwm' (i386). (lldb) r error: process launch failed: Lost debug server connection (lldb) Plz answer about this problem Thank you. --- 이 이메일은 Avast 안티바이러스 소프트웨어로 바이러스 검사를 완료했습니다. https://www.avast.com/antivirus ___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev