wasmtime / Issue #932 DWARF-5 support · git-wasmtime

Stream: git-wasmtime

Topic: wasmtime / Issue #932 DWARF-5 support

Wasmtime GitHub notifications bot (Apr 28 2020 at 00:02):

ggreif edited Issue #932:

I gather that the Wasm DWARF spec defines DWARF-5 as the baseline debug format.

However several sections from Version 5 are rejected by wasmtime with panics. E.g.
https://github.com/bytecodealliance/wasmtime/blob/master/crates/debug/src/read_debuginfo.rs#L63

For my purposes ".debug_rnglists" is the most important.

Is there any ETA for supporting these?

Note: The clang-10 compiler (currently in rc1) doesn't reliably emit DWARF-5 yet.

clang-11 (pre-release) seems to generate DWARF-5 without crashing.

Wasmtime GitHub notifications bot (Apr 28 2020 at 00:04):

ggreif edited Issue #932:

I gather that the Wasm DWARF spec defines DWARF-5 as the baseline debug format.

However several sections from Version 5 are rejected by wasmtime with panics. E.g.
https://github.com/bytecodealliance/wasmtime/blob/master/crates/debug/src/read_debuginfo.rs#L63

For my purposes ".debug_rnglists" is the most important.

Is there any ETA for supporting these?

Note: The clang-10 compiler (currently in rc1) doesn't reliably emit DWARF-5 yet.

clang-11 (pre-release) seems to generate DWARF-5 without crashing. As per #1410 the DWARF example Wasm files are compiled with this clang.

Wasmtime GitHub notifications bot (Apr 28 2020 at 01:49):

ggreif edited Issue #932:

Next milestone is Exprloc support for the Wasm-style locations. I'll try to put together a PR next.

So far I see following problems:

no operand stack locations yet (middle-term)

index needs (seems) to begin at 1 (I'd expect 0) to obtain valid ranges

ranges get discarded because not being sufficiently populated with labels.

OUTDATED info below.

I gather that the Wasm DWARF spec defines DWARF-5 as the baseline debug format.

However several sections from Version 5 are rejected by wasmtime with panics. E.g.
https://github.com/bytecodealliance/wasmtime/blob/master/crates/debug/src/read_debuginfo.rs#L63

For my purposes ".debug_rnglists" is the most important.

Is there any ETA for supporting these?

Note: The clang-10 compiler (currently in rc1) doesn't reliably emit DWARF-5 yet.

clang-11 (pre-release) seems to generate DWARF-5 without crashing. As per #1410 the DWARF example Wasm files are compiled with this clang.

Wasmtime GitHub notifications bot (Apr 28 2020 at 01:50):

ggreif edited Issue #932:

Current Goal

Next milestone is Exprloc support for the Wasm-style locations. I'll try to put together a PR next.

So far I see following problems:

no operand stack locations yet (middle-term)

index needs (seems) to begin at 1 (I'd expect 0) to obtain valid ranges

ranges get discarded because not being sufficiently populated with labels.

OUTDATED info below

I gather that the Wasm DWARF spec defines DWARF-5 as the baseline debug format.

However several sections from Version 5 are rejected by wasmtime with panics. E.g.
https://github.com/bytecodealliance/wasmtime/blob/master/crates/debug/src/read_debuginfo.rs#L63

For my purposes ".debug_rnglists" is the most important.

Is there any ETA for supporting these?

Note: The clang-10 compiler (currently in rc1) doesn't reliably emit DWARF-5 yet.

clang-11 (pre-release) seems to generate DWARF-5 without crashing. As per #1410 the DWARF example Wasm files are compiled with this clang.

Wasmtime GitHub notifications bot (Apr 28 2020 at 14:04):

ggreif edited Issue #932:

Current Goal

Next milestone is Exprloc support for the Wasm-style locations. I'll try to put together a PR next.

So far I see following problems:

no operand stack locations yet (middle-term)

index needs (seems) to begin at 1 (I'd expect 0) to obtain valid ranges

ranges get discarded because not being sufficiently populated with labels.

accept .debug_types (middle-term)

OUTDATED info below

I gather that the Wasm DWARF spec defines DWARF-5 as the baseline debug format.

However several sections from Version 5 are rejected by wasmtime with panics. E.g.
https://github.com/bytecodealliance/wasmtime/blob/master/crates/debug/src/read_debuginfo.rs#L63

For my purposes ".debug_rnglists" is the most important.

Is there any ETA for supporting these?

Note: The clang-10 compiler (currently in rc1) doesn't reliably emit DWARF-5 yet.

clang-11 (pre-release) seems to generate DWARF-5 without crashing. As per #1410 the DWARF example Wasm files are compiled with this clang.

Wasmtime GitHub notifications bot (Apr 28 2020 at 14:06):

ggreif edited Issue #932:

Current Goal

The upcoming milestone is Exprloc support for the Wasm-style locations. I'll try to put together a PR next.

So far I see following problems:

no operand stack locations yet (middle-term)

index needs (seems) to begin at 1 (I'd expect 0) to obtain valid ranges

ranges get discarded because not being sufficiently populated with labels.

Next Goal

accept .debug_types (middle-term)

OUTDATED info below

I gather that the Wasm DWARF spec defines DWARF-5 as the baseline debug format.

However several sections from Version 5 are rejected by wasmtime with panics. E.g.
https://github.com/bytecodealliance/wasmtime/blob/master/crates/debug/src/read_debuginfo.rs#L63

For my purposes ".debug_rnglists" is the most important.

Is there any ETA for supporting these?

Note: The clang-10 compiler (currently in rc1) doesn't reliably emit DWARF-5 yet.

clang-11 (pre-release) seems to generate DWARF-5 without crashing. As per #1410 the DWARF example Wasm files are compiled with this clang.

Wasmtime GitHub notifications bot (Apr 28 2020 at 17:07):

ggreif edited Issue #932:

Current Goal

The upcoming milestone is Exprloc support for the Wasm-style locations. I'll try to put together a PR next.

So far I see following problems (possibly related to https://github.com/bytecodealliance/wasmtime/issues/1613):

no operand stack locations yet (middle-term)

index needs (seems) to begin at 1 (I'd expect 0) to obtain valid ranges

ranges get discarded because not being sufficiently populated with labels.

Next Goal

accept .debug_types (middle-term)

OUTDATED info below

I gather that the Wasm DWARF spec defines DWARF-5 as the baseline debug format.

However several sections from Version 5 are rejected by wasmtime with panics. E.g.
https://github.com/bytecodealliance/wasmtime/blob/master/crates/debug/src/read_debuginfo.rs#L63

For my purposes ".debug_rnglists" is the most important.

Is there any ETA for supporting these?

Note: The clang-10 compiler (currently in rc1) doesn't reliably emit DWARF-5 yet.

clang-11 (pre-release) seems to generate DWARF-5 without crashing. As per #1410 the DWARF example Wasm files are compiled with this clang.

Wasmtime GitHub notifications bot (Apr 28 2020 at 20:24):

ggreif edited Issue #932:

Current Goal

The upcoming milestone is Exprloc support for the Wasm-style locations. I'll try to put together a PR next.

So far I see following problems (possibly related to https://github.com/bytecodealliance/wasmtime/issues/1613):

no operand stack locations yet (middle-term)

index needs (seems) to begin at 1 (I'd expect 0) to obtain valid ranges

[x] (potentially resolved by https://github.com/bytecodealliance/wasmtime/pull/1572) ranges get discarded because not being sufficiently populated with labels.

Next Goal

accept .debug_types (middle-term)

OUTDATED info below

I gather that the Wasm DWARF spec defines DWARF-5 as the baseline debug format.

However several sections from Version 5 are rejected by wasmtime with panics. E.g.
https://github.com/bytecodealliance/wasmtime/blob/master/crates/debug/src/read_debuginfo.rs#L63

For my purposes ".debug_rnglists" is the most important.

Is there any ETA for supporting these?

Note: The clang-10 compiler (currently in rc1) doesn't reliably emit DWARF-5 yet.

clang-11 (pre-release) seems to generate DWARF-5 without crashing. As per #1410 the DWARF example Wasm files are compiled with this clang.

Wasmtime GitHub notifications bot (Apr 30 2020 at 17:46):

yurydelendik commented on Issue #932:

@ggreif is anything else left to close this particular issue? I see .debug_types and "operand stack locations". I would suggest to open a separate issue for the latter to track it with https://reviews.llvm.org/D78818.

Wasmtime GitHub notifications bot (Apr 30 2020 at 19:22):

ggreif commented on Issue #932:

I have my own heap of problems, with my compiler. Happy to close this one.

Wasmtime GitHub notifications bot (Apr 30 2020 at 19:22):

ggreif closed Issue #932:

Current Goal

The upcoming milestone is Exprloc support for the Wasm-style locations. I'll try to put together a PR next.

So far I see following problems (possibly related to https://github.com/bytecodealliance/wasmtime/issues/1613):

no operand stack locations yet (middle-term)

index needs (seems) to begin at 1 (I'd expect 0) to obtain valid ranges

[x] (potentially resolved by https://github.com/bytecodealliance/wasmtime/pull/1572) ranges get discarded because not being sufficiently populated with labels.

Next Goal

accept .debug_types (middle-term)

OUTDATED info below

I gather that the Wasm DWARF spec defines DWARF-5 as the baseline debug format.

However several sections from Version 5 are rejected by wasmtime with panics. E.g.
https://github.com/bytecodealliance/wasmtime/blob/master/crates/debug/src/read_debuginfo.rs#L63

For my purposes ".debug_rnglists" is the most important.

Is there any ETA for supporting these?

Note: The clang-10 compiler (currently in rc1) doesn't reliably emit DWARF-5 yet.

clang-11 (pre-release) seems to generate DWARF-5 without crashing. As per #1410 the DWARF example Wasm files are compiled with this clang.

Last updated: Dec 23 2024 at 13:07 UTC