Vincent Laviron

I looked at the lldb sources and apparently there is a `-r` option to `br s` that uses regexps instead of full names. Does it actually work (I can't tell...

> Personally I think we should revert to the previous convention using `__`. Even if there are potential workarounds in debuggers such as mentioned in #12274, this seems likely to...

> ("tweak the OCaml naming scheme": I would try to take the `ocamlopt -s` assembly output of a module that uses these dotted symbols, edit the textual assembly file to...

I am broadly in favour too, although I don't think the "closure-free" version is useful (it does not guarantee the absence of closures, and if you have more than one...

What about `val to_slice : t -> bytes * int * int` ? I think it's better than the previous PR because it makes it clear which part of the...

Isn't this part of the manual also relevant for `ocamlopt` ? In this case, this is not a reference, this is actual inclusion of the runtime. For bytecode, it has...

Also, if using perf with OCaml 5 you should not use `--call-graph dwarf`. It is very slow, and the split stack between C and OCaml tends to confuse it so...

The problem seems to occur during the initialisation of the `Uunf_data` module. If this is a bug in the compiler and not the runtime, you should be able to reproduce...

I've created a PR with a potential fix at #12485. I haven't yet reproduced the issue on my computer, so if someone who has already done the setup could check...

I finally managed to test my PR on the repro case. I confirm that I could reproduce the error, and that adding my commit to the top of the 5.1...