I'm building a C wasm app using emscripten. I'm using emscripten 3.1.45. I was able to debug the C wasm modules in Chrome, and I could see the C source files in the "Sources" tab of Chrome developer tools. This was working until version 132. In version 133, it simply stops working, without any error or warning. In this version, I can only see the javascript files and none of the C wasm modules.
Does anyone know what happened? Did chrome stopped working with "C/C++ DevTools Support (DWARF)" ?
I went back to version 131 and it went back to working as before.
I created a bug on google issue tracker here
Short answer: right now, it works in the current Canary build.
I received a response that they knew about the issue the issue and is already fixed for Chrome 134. However as I'm writing this, it is not yet released neither on the Beta nor on the Dev version but it is fixed on the nightly Canary build. The current versions I've tested:
The Chromium bug fix has been verified on 135.0.7001.0 and it looks to be merged to v134 although not yet released, apparently. Looking at the cadence of beta releases, I think there will be a beta release tomorrow that will include it. There is a merge request for v133 to so a hotfix might come too to stable as well.