[lldb-dev] Debugging win64 from 32bits
Hi, Is there a good way to debug win64 from a win32 process? Or is there an "lldb-debugserver" that works on windows that can aid in this process? -- Carlo Kok ___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] Debugging win64 from 32bits
No, there is no such thing currently. You can build an x64 lldb, it should work in theory but it's not well tested. If you want to port llgs to Windows that would be great :) On Tue, Apr 19, 2016 at 7:40 AM Carlo Kok via lldb-dev < lldb-dev@lists.llvm.org> wrote: > Hi, > > Is there a good way to debug win64 from a win32 process? > > Or is there an "lldb-debugserver" that works on windows that can aid in > this process? > > -- > Carlo Kok > ___ > 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] [Bug 27423] New: test infra: clear file-level test results on any test files being rerun prior to starting the rerun
https://llvm.org/bugs/show_bug.cgi?id=27423 Bug ID: 27423 Summary: test infra: clear file-level test results on any test files being rerun prior to starting the rerun Product: lldb Version: unspecified Hardware: PC OS: All Status: NEW Severity: normal Priority: P Component: All Bugs Assignee: lldb-dev@lists.llvm.org Reporter: todd.fi...@gmail.com CC: llvm-b...@lists.llvm.org Classification: Unclassified The test rerun logic will charge timeouts and exceptional exits to the file if and only if the dotest.py inferior was not in the middle of running a test method when the timeout or exceptional exit occurred. In these cases, it is impossible for a *successful* rerun to clear that file-level event since the successful rerun will simply overwrite test-method test results, not file-level results. The simple solution here is to take the set of files that are scheduled for rerun, and clear any file-level test result for them. If the file-level event that was charged previously is deterministically repeating, it will occur again and we will not lose it. In the meantime, we allow the rerun to clear the file-level event so that successful reruns come back clean. -- 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 27423] test infra: clear file-level test results on any test files being rerun prior to starting the rerun
https://llvm.org/bugs/show_bug.cgi?id=27423 Todd Fiala changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|lldb-dev@lists.llvm.org |todd.fi...@gmail.com --- Comment #1 from Todd Fiala --- Here was one such example: http://lab.llvm.org:8011/builders/lldb-x86_64-darwin-13.4/builds/9770 -- 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
Re: [lldb-dev] Debugging win64 from 32bits
> On Apr 19, 2016, at 8:58 AM, Zachary Turner via lldb-dev > wrote: > > No, there is no such thing currently. You can build an x64 lldb, it should > work in theory but it's not well tested. > > If you want to port llgs to Windows that would be great :) I second this. Taking the guts or ProcessWindows and making an lldb-server port for windows would really help out windows development. It would allow remote debugging of windows machines, it would allow us to implement both the debugging and platform aspects of lldb-server, and also allow remote debugging from other systems to windows machines. Greg Clayton ___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
[lldb-dev] [Bug 26267] IncompleteModulesTestCase asserting in clang on Darwin with Xcode 7.3 Beta 1
https://llvm.org/bugs/show_bug.cgi?id=26267 Bruno Cardoso Lopes changed: What|Removed |Added Status|NEW |RESOLVED CC||bruno.card...@gmail.com Resolution|--- |DUPLICATE --- Comment #2 from Bruno Cardoso Lopes --- *** This bug has been marked as a duplicate of bug 27186 *** -- 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
