calixteman

The strings: https://github.com/arturadib/botio/blob/9434ca0ede20307f7e1d6efa7e9e559240d72f70/lib/module.js#L104-L108 especially the `jobInfo.head_ref` must be protected. For example if it's `foo&bar` the ampersand will be interpreted by bash.

Don't return an error when some section are not correct

4

I have a debug file (IBM935.so.debug) which contains some incorrect info in dynamic section and so the section failed to be parsed with error `Invalid PT_DYNAMIC size (offset 0x14db0, filesz...

Unrelated to this change, but in looking to the code for js, I think we (I ??) missed to add operators like `??` and `?.` (maybe others ?): they're lazy...

When all languages will be available in crates, we can then build a version of rca with specific moz-languages and "normal" languages for normal released version.

The code itself can be non-utf8. So inspect all the code to find code to string and remove what is useless.

Add the possibility to configure the demangler with all available options

2

Right now, we just have two possibilities: Full or Short. It'd be nice to be able to select the flags we want to demangle.

Macro annotations

9

In firefox code, we use some macros to make annotations (for clang static analysis for example). For example: https://searchfox.org/mozilla-central/source/dom/animation/AnimationTarget.h#54 or https://searchfox.org/mozilla-central/source/mfbt/CheckedInt.h#510 Such annotations lead to parse errors and I understand...