Stream: git-wasmtime

Topic: wasmtime / Issue #1850 JIT debugging not activated window...

Wasmtime GitHub notifications bot (Jun 09 2020 at 21:40):

adv-sw opened Issue #1850:

• What are the steps to reproduce the issue?

1. Build fib_debug, windows or use version here : http://advance-software.com/misc/fib_debug.zip

2. Open using lldb from llvm 10.0 release, windows.

3. Step into the app until just prior to the fib run invocation.

4. Note no JIT info when "image list" command is run from lldb

https://pastebin.com/mTxufwp9

wasmtime from here : https://github.com/bytecodealliance/wasmtime/releases/tag/dev

on 9th June 2020. specific version unknown.

environment: windows 10, x64, visual studio 2019.

Wasmtime GitHub notifications bot (Jun 09 2020 at 21:40):

adv-sw labeled Issue #1850:

• What are the steps to reproduce the issue?

1. Build fib_debug, windows or use version here : http://advance-software.com/misc/fib_debug.zip

2. Open using lldb from llvm 10.0 release, windows.

3. Step into the app until just prior to the fib run invocation.

4. Note no JIT info when "image list" command is run from lldb

https://pastebin.com/mTxufwp9

wasmtime from here : https://github.com/bytecodealliance/wasmtime/releases/tag/dev

on 9th June 2020. specific version unknown.

environment: windows 10, x64, visual studio 2019.

Wasmtime GitHub notifications bot (Jun 25 2020 at 13:00):

yurydelendik labeled Issue #1850:

• What are the steps to reproduce the issue?

1. Build fib_debug, windows or use version here : http://advance-software.com/misc/fib_debug.zip

2. Open using lldb from llvm 10.0 release, windows.

3. Step into the app until just prior to the fib run invocation.

4. Note no JIT info when "image list" command is run from lldb

https://pastebin.com/mTxufwp9

wasmtime from here : https://github.com/bytecodealliance/wasmtime/releases/tag/dev

on 9th June 2020. specific version unknown.

environment: windows 10, x64, visual studio 2019.

Wasmtime GitHub notifications bot (Jul 02 2020 at 16:45):

yurydelendik commented on Issue #1850:

I could not compile latest lldb by myself. I tried VSCode + CodeLLDB for Windows and it worked as expected.


Please ensure you are using proper version of LLDB that can function on Windows and supports GDB JIT interface.

Wasmtime GitHub notifications bot (Jul 02 2020 at 18:03):

yurydelendik unlabeled Issue #1850:

• What are the steps to reproduce the issue?

1. Build fib_debug, windows or use version here : http://advance-software.com/misc/fib_debug.zip

2. Open using lldb from llvm 10.0 release, windows.

3. Step into the app until just prior to the fib run invocation.

4. Note no JIT info when "image list" command is run from lldb

https://pastebin.com/mTxufwp9

wasmtime from here : https://github.com/bytecodealliance/wasmtime/releases/tag/dev

on 9th June 2020. specific version unknown.

environment: windows 10, x64, visual studio 2019.

Wasmtime GitHub notifications bot (Jul 05 2020 at 11:59):

adv-sw commented on Issue #1850:

Please ensure you are using proper version of LLDB that can function on Windows and supports GDB JIT interface.

Thanks, Yuri.

Please could you more formally specify the most recent version of LLDB that functions on Windows & supports GDB JIT interface. I.e. Please provide a link to exactly what you installed. Could be GDB JIT is a compile time option I didn't have enabled. Dunno. Time to revisit.

Wasmtime GitHub notifications bot (Jul 05 2020 at 12:01):

adv-sw edited a comment on Issue #1850:

Please ensure you are using proper version of LLDB that can function on Windows and supports GDB JIT interface.

Thanks, Yury.

Please could you more formally specify the most recent version of LLDB that functions on Windows & supports GDB JIT interface. I.e. Please provide a link to exactly what you installed. Could be GDB JIT is a compile time option I didn't have enabled. Dunno. Time to revisit.

Wasmtime GitHub notifications bot (Jul 06 2020 at 14:34):

yurydelendik commented on Issue #1850:

Please provide a link to exactly what you installed.

• https://code.visualstudio.com/
• https://marketplace.visualstudio.com/items?itemName=vadimcn.vscode-lldb

Could be GDB JIT is a compile time option I didn't have enabled.

I don't know what was done on your end. The only VSCode settings I switched on is Allow setting breakpoints in any file, but it can be done via breakpoints panel.

Wasmtime GitHub notifications bot (Jul 06 2020 at 14:35):

yurydelendik edited a comment on Issue #1850:

Please provide a link to exactly what you installed.

• https://code.visualstudio.com/
• https://marketplace.visualstudio.com/items?itemName=vadimcn.vscode-lldb

Could be GDB JIT is a compile time option I didn't have enabled.

I don't know what was done on your end. The only VSCode settings I switched on is Allow setting breakpoints in any file, but it can be done via breakpoints panel.

Last updated: Dec 23 2024 at 12:05 UTC