Anansi

> Thanks for your question. To diagnose this further we'll need at least the `build-tracer.log` file created during the build. This file can be found in the `D:\chromium\99.0.4844.84\db\log`. You might...

> Thanks for the log. Could you also share the output of `d:\chromium\99.0.4844.84\src\third_party\llvm-build\release+asserts\bin\clang-cl.exe -Xclang -dM -E SomeEmptyFile.cpp`, where `SomeEmptyFile.cpp` is some empty file you should create. I created an empty...

> Thanks. This looks ok. For some reason we are not picking up on the `#define _MSC_VER ...` in that output stopping the extraction from running. This is the `Command-line...

> Thanks. This also looks ok. I'm slightly puzzled by this. I think we need to try running codeql slightly differently unpacking the steps `database create` does under the hood....

> Thanks. This seems to be an omission in our extractor code. We're not propagating the value of `_MSC_VER`. I think this should be easy to fix. Ok, Thanks

> I've checked internally if there might be a workaround, but there doesn't really seem to be one unless you're prepared to start modifying Chromium's build system. > > I'll...

> Thanks for the report! This looks like the parser is failing, could you run it manually and check where/why it fails: `node --trace-uncaught Sources/Fuzzilli/Compiler/Parser/parser.js Sources/Fuzzilli/Protobuf/ast.proto path/to/code.js /tmp/ast.proto`? ``` >node...

Hi, has this issue been fixed? > Ah right, so probably the reason is that the parser doesn't currently support parameters with default values: https://github.com/googleprojectzero/fuzzilli/blob/main/Sources/Fuzzilli/Compiler/Parser/parser.js#L76 (you could `dump(param)` before that...