Normally symbols are read from the DSO and adjusted, if need be, so thatthe symbol start matches the file offset in the DSO file (we want thefile offset because that is what we know from MMAP events). That is doneby dso__load_sym() which inserts the symbols *after* adjusting them.

In the case of kcore, the symbols have been read from kallsyms and thesymbol start is the memory address. The symbols have to be adjusted tomatch the kcore file offsets. dso__split_kallsyms_for_kcore() does that,but now the adjustment is being done *after* the symbols have beeninserted. It appears dso__split_kallsyms_for_kcore() was assuming thatchanging the symbol start would not change the order in the rbtree -which is, of course, not guaranteed.