4 ms·

Yup, it's mostly just the story and tools we used to get ourselves out of a mess that was made harder by some decisions made earlier -- the tests were running i

Yup, it's mostly just the story and tools we used to get ourselves out of a mess that was made harder by some decisions made earlier -- the tests were running in a container with stripped symbols (we're going to ship symbols after this, no reason to over-optimize), our custom test runner failed to report process death (an oversight). There's no reason setenv should have been called here. The `openssl-probe` library could simply return the paths to the system cert files and callers could plug those directly into the OpenSSL config. Oversights all around and hopefully this continues to improve.

mark_undoio 2y ago
> Yup, it's mostly just the story and tools we used to get ourselves out of a mess that was made harder by some decisions made earlier -- the tests were running in a container with stripped symbols (we're going to ship symbols after this, no reason to over-optimize) It's worth noting here that you can also build your binaries and keep debug symbols separately. You don't need to ship them with the binary (although it will make many scenarios a bit simpler if you do, since you'll always have the right ones available). Some info that might help: https://www.tweag.io/blog/2023-11-23-debug-fission/ https://www.tweag.io/blog/2023-11-23-debug-fission/ https://undo.io/resources/gdb-watchpoint/reduce-binary-size-compile-time-split-dwarf/ https://undo.io/resources/gdb-watchpoint/reduce-binary-size-...
nemetroid 2y ago
> we're going to ship symbols after this, no reason to over-optimize You might want to look into debuginfod.