]> feistymeow.org Git - feisty_meow.git/commit
build fully working with callstack tracker
authorFred T. Hamster <fred@feistymeow.org>
Wed, 18 Feb 2026 00:39:45 +0000 (19:39 -0500)
committerFred T. Hamster <fred@feistymeow.org>
Wed, 18 Feb 2026 00:39:45 +0000 (19:39 -0500)
commit53a35e36b496cf9770b7f3a7cc0ecfd4c7d0707a
tree978dcef6d5acf95a8b99697273c133705e6914d9
parent78e9cd34891db12f7be2b000459fb9dc61646429
build fully working with callstack tracker

just had a totally successful build for the first time in a while, and this is with the callstack tracker enabled.
it does seem that our threaded woes with the callstack code were due to our attempting to use thread local for the tracker;
it needs to persist past the end of the thread to avoid gnarly shutdown issues with the static objects, like the synchronizer,
which was also thread local for some reason.  now we just use a program wide object to list the thread-wide callstack
trackers, and it's nice and fast due to using the standard library unordered_map.  was using our own hash table, but there are
too many intertwined things with the callstack tracker for that to be a good option, so standard template library it is.
nucleus/library/application/callstack_tracker.cpp
nucleus/library/structures/hash_table.h
nucleus/library/structures/int_hash.h
octopi/library/sockets/sequence_tracker.cpp
octopi/library/tests_octopus/makefile
production/feisty_meow_config.ini
scripts/clam/target_runner.sh