For now you also need to use the temporary flag -gforce_dwarf to actually get the dwarf output. Beware that you are on the bleeding edge if you do this. The Chrome devtools debugger is still missing things like inspecting variable values as well. Eventually that flag will go away and we'll have some reasonable behavior for the regular -g flag and a couple of related flags.
On Wed, Jan 29, 2020 at 3:21 PM Alon Zakai <[email protected]> wrote: > 1. Yes, if you just use clang, then it can emit DWARF, and that will be > valid, if you don't yourself manually run another tool after clang. > > 2. However, as of last night there *is* support for DWARF in binaryen, so > using emscripten will work, at least in debug builds (binaryen will update > the DWARF in every optimization it performs). Only in a tip of tree build > for now (emsdk install tot). > > > On Wed, Jan 29, 2020 at 6:54 AM Benjamin Golinvaux <[email protected]> wrote: > >> Hello >> >> In this Chrome announcement where support for DWARF is introduced ( >> https://developers.google.com/web/updates/2019/12/webassembly), I can >> see this at the end of the page : >> >> *"There is still quite a bit of work to do though. For example, on the >> tooling side, Emscripten (Binaryen) and wasm-pack (wasm-bindgen) don’t >> support updating DWARF information on transformations they perform yet. For >> now, they won’t benefit from this integration."* >> >> However, am I correct in assuming that if I use clang directly and don't >> use binding generation, binaryen is not used and that my binaries should >> contain DWARF debug info? Maybe the Chrome team is referring to the >> previous backend? >> >> (I'd *very* much like to be able to debug my native code that sometimes >> behaves differently in wasm than it does in the native project I am using >> for debugging purposes :) >> >> Thanks in advance >> >> Benjamin >> >> >> >> >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "emscripten-discuss" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/emscripten-discuss/46e7c6de-57f6-4cc1-a0b9-6f29dd785ce2%40googlegroups.com >> <https://groups.google.com/d/msgid/emscripten-discuss/46e7c6de-57f6-4cc1-a0b9-6f29dd785ce2%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- > You received this message because you are subscribed to the Google Groups > "emscripten-discuss" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/emscripten-discuss/CAEX4NpQtZ1xM56%2BSN1dtnNBvB%2B3vyWQwXkTO%2B84ubtPmZmb1Kw%40mail.gmail.com > <https://groups.google.com/d/msgid/emscripten-discuss/CAEX4NpQtZ1xM56%2BSN1dtnNBvB%2B3vyWQwXkTO%2B84ubtPmZmb1Kw%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "emscripten-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/emscripten-discuss/CAAEAhvd-Rizs5tHkKZrMeC6dH9uprETqmpn-%3D%2BkMGJwDJkeqBQ%40mail.gmail.com.
