[lldb-dev] LLDB/NetBSD report May/2018: Coverage of signal routines in the kernel in the context of ptrace(2)
The number of ATF ptrace(2) tests cases has been significantly incremented, however there is still a substantial amount of work to be done and a number of serious bugs to be resolved. With fixes and addition of new test cases, as of today we are passing 1,206 (last month: 961) ptrace(2) tests and skipping 1 (out of 1,256 total; last month: 1,018 total). No counted here tests that appeared outside the ptrace(2) context. Plan for the next milestone: Cover with regression tests remaining elementary scenarios of handling crash signals. Fix known bugs in the NetBSD kernel. Follow up the process with the remaining fork(2) and vfork(2) scenarios. This work was sponsored by The NetBSD Foundation. http://blog.netbsd.org/tnf/entry/coverage_of_signal_routines_in signature.asc Description: OpenPGP digital signature ___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
[lldb-dev] [Bug 37496] Sometimes LLDB freeze after launching process
https://bugs.llvm.org/show_bug.cgi?id=37496 Stella Stamenova changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED CC||sti...@microsoft.com --- Comment #1 from Stella Stamenova --- This is fixed in commit rL333781: [lldb, process] Fix occasional hang when launching a process in LLDB -- You are receiving this mail because: You are the assignee for the bug.___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
[lldb-dev] [Bug 37656] New: lit/Expr/TestIRMemoryMap.test does not work on Windows
https://bugs.llvm.org/show_bug.cgi?id=37656 Bug ID: 37656 Summary: lit/Expr/TestIRMemoryMap.test does not work on Windows Product: lldb Version: unspecified Hardware: PC OS: All Status: NEW Severity: normal Priority: P Component: All Bugs Assignee: lldb-dev@lists.llvm.org Reporter: v...@apple.com CC: llvm-b...@lists.llvm.org lldb-test fails to create a process that's usable by the JIT. -- You are receiving this mail because: You are the assignee for the bug.___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
[lldb-dev] [Bug 37658] New: LLDB does not correctly handle frames other than frame 0 on Windows
https://bugs.llvm.org/show_bug.cgi?id=37658 Bug ID: 37658 Summary: LLDB does not correctly handle frames other than frame 0 on Windows Product: lldb Version: 6.0 Hardware: PC OS: Windows NT Status: NEW Severity: normal Priority: P Component: All Bugs Assignee: lldb-dev@lists.llvm.org Reporter: sti...@microsoft.com CC: llvm-b...@lists.llvm.org There are a couple of related bugs already filed: https://bugs.llvm.org/show_bug.cgi?id=37495 is for register read specifically https://bugs.llvm.org/show_bug.cgi?id=26265 is for evaluating arguments But this is not the extent of the issue. Even the number of the frames that LLDB reports is not always correct. For example, the test TestGuessLanguage.py tries to access a frame that is not frame 0 and it gets an index of range exception. -- You are receiving this mail because: You are the assignee for the bug.___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
