sam5d ago
Sergei Trofimovich

Over past few weeks `gcc` from `master` was crashing on all sorts of `c++` projects with suspiciously similar backtraces: `SIGSEGV` in `ggc_set_mark() / gt_ggc_mx_lang_tree_node()`.

Took me some time to find the culprit and have a workaround to stop the crashes.

Guess where the fix hides!

Spoiler: https://trofi.github.io/posts/347-another-memory-corruption-case.html

another memory corruption case

Apr 2 at 10:21pmWeb
Show threadpenguin426d ago
@trofi gcc has always been good at tickling bad memory; one idea has been that it chases a lot of pointers.
Show threadAndrea (Drea) Tamar Pinski6d ago
@penguin42 @trofi Well mark part of a garbage collector is always just that, chasing pointers :).
Most data structures link to the next one. Though it is not always transversing those pointers but the garbage collector will :).
Show threadAlexander Monakov5d ago
@trofi if you have the time, please try stressapptest with the -W flag, it tends to uncover issues much faster (although might not in your case): https://mastodon.gamedev.place/@amonakov/115980559099496812