On Di, 06.11.18 11:57, juice (ju...@swagman.org) wrote: > > Hi, > > During the past half year I have seen systemd dump core three times due > to what I suspect a hashmap corruption or race. > Each time it looks a bit different and is triggered by different things > but it somehow centers on hashmap operations. > > What would be the prefered way to debug this? I cannot add huge logging > as this is something that happens once in a blue moon and always in > different compute nodes. > Is there some way I could easily test it by increasing the chance of such > corruption/race happening?
This looks very much like a memory corruption of some sorts and valgrind should be the tool of choice to track that down. Lennart -- Lennart Poettering, Red Hat _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
