Actually, its not doing exactly after a copyover. What I'm doing is kind of a long way around, but...:
1) In a normally booted version(no valgrind), do "hotboot debug" to generate the files that would be need.
2) Shutdown mud now
3) then, I boot the mud using: "valgrind -v --leak-check=yes --show-reachable=yes --gdb-attach=yes --num-callers=10 ../src/swr 4000 valgrind "
Adding the "vagrind" argument to it. When main detects that its valgrind, as opposed to "hotboot" or nothing, it will do a normal boot, initializing port and such, and then call hotboot_recover to read all the files. It it effectively the same thing as having valgrind working across a copyover, more work and a little more processor, but it basically works accomplishes the same thing, allowing valgrind to check the hotboot_recover code, which is where I am having the problem with my own code.