<html>
<head>
<base href="https://bugs.llvm.org/">
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - lldb/jit not working Windows"
href="https://bugs.llvm.org/show_bug.cgi?id=51832">51832</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>lldb/jit not working Windows
</td>
</tr>
<tr>
<th>Product</th>
<td>lldb
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</td>
</tr>
<tr>
<th>Hardware</th>
<td>PC
</td>
</tr>
<tr>
<th>OS</th>
<td>Windows NT
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>release blocker
</td>
</tr>
<tr>
<th>Priority</th>
<td>P
</td>
</tr>
<tr>
<th>Component</th>
<td>All Bugs
</td>
</tr>
<tr>
<th>Assignee</th>
<td>lldb-dev@lists.llvm.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>steve@advance-software.com
</td>
</tr>
<tr>
<th>CC</th>
<td>jdevlieghere@apple.com, llvm-bugs@lists.llvm.org
</td>
</tr></table>
<p>
<div>
<pre>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 :
<a href="https://www.youtube.com/watch?v=PevI_Mn-UUE">https://www.youtube.com/watch?v=PevI_Mn-UUE</a>
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 : <a href="https://controlc.com/40a36c4d">https://controlc.com/40a36c4d</a>
... 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 :
<a href="https://github.com/bytecodealliance/wasmtime/releases/tag/v0.29.0">https://github.com/bytecodealliance/wasmtime/releases/tag/v0.29.0</a>
... in addition to the fizzbuzz.zip attachment which provides reproducible test
files & executibles on Windows.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>