[lldb-dev] [Bug 51832] New: lldb/jit not working Windows
https://bugs.llvm.org/show_bug.cgi?id=51832 Bug ID: 51832 Summary: lldb/jit not working Windows Product: lldb Version: unspecified Hardware: PC OS: Windows NT Status: NEW Severity: release blocker Priority: P Component: All Bugs Assignee: lldb-dev@lists.llvm.org Reporter: st...@advance-software.com CC: jdevliegh...@apple.com, llvm-b...@lists.llvm.org Web Assembly (wasmtime) JIT debugging via lldb GDP/JIT interface not working on Windows (trunk). Confirmed works Linux (llvm 10 - trunk status currently unknown on Linux). Tried the following on Windows, using llvm trunk : https://www.youtube.com/watch?v=PevI_Mn-UUE On Windows (running Windows 11 pre-release), the breakpoint isn't hit despite it being the exact same test. Tried llvm lldb/jit unit test on Windows. I get the following : https://controlc.com/40a36c4d ... from executing test directly. Specific test filtered using : set LIT_FILTER=Breakpoint/jit-loader_rtdyld_elf.test Unit test fails. Failure appears to be in lli which sets up the test environment. It appears we have 2 bugs. 1. JIT breakpoints not getting hit 2. lli failing meaning unit test can't complete to confirm or otherwise whether JIT debugging is working on Windows. The following appeared to complete successfully - indicating required plugin available. (lldb) settings set plugin.jit-loader.gdb.enable on However available & functioning are not the same thing. To run same test on Linux - to confirm wasmtime is setting up debug environment correctly, the following can be used - binary or buld from source : https://github.com/bytecodealliance/wasmtime/releases/tag/v0.29.0 ... in addition to the fizzbuzz.zip attachment which provides reproducible test files & executibles on Windows. -- You are receiving this mail because: You are the assignee for the bug.___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
[lldb-dev] [Bug 51833] New: TestGuiBasicDebug.py is flaky - lack of process event synchronization ?
https://bugs.llvm.org/show_bug.cgi?id=51833 Bug ID: 51833 Summary: TestGuiBasicDebug.py is flaky - lack of process event synchronization ? Product: lldb Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P Component: All Bugs Assignee: lldb-dev@lists.llvm.org Reporter: lab...@google.com CC: jdevliegh...@apple.com, llvm-b...@lists.llvm.org Once every while, the "finish" command in the test fails to step out of the designated function. Or rather, it fails to stop after stepping out of the function -- instead, it continues stepping until the application terminates. My analysis of the test logs (see attachment) suggests that this if due to poor event handling discipline. After requesting an (asynchronous) step out, the gui command goes back to its normal business. The first order of business is usually to redraw the screen (see Application::Run). If it does that too quickly, it can happen that the command will start drawing the threads before the "running" event propagates to public. This means that the all the StateIsStoppedState guards that the command uses to prevent accessing a running process will fail. This will cause lldb to start computing (a bogus) the stack frame list in parallel to its internal processing of the step over operation. When the inferior stops, the step over thread plan will be presented with the inconsistent stack frame, which will cause it to think that it has _not_ stepped out of the function, and will trigger another resume. That will terminate the inferior. It's not fully clear to me how to fix this. Presumably, the gui should process the running event resulting from the resume command before doing anything else. It has some code which tries to do that, but since it only does a poll, it will not capture the event if it has not been already sent. It also seems that the process run lock should have prevented anyone from tampering with the process while it was running. -- You are receiving this mail because: You are the assignee for the bug.___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
[lldb-dev] 13.0.0-rc3 has been tagged
Hi, I've tagged 13.0.0-rc3. This will likely be the last rc unless there are critical bugs that are found. Please test the release and report results. -Tom ___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
