During the snapshot process, we used to traverse the proc self tree and match its intervals with those in pageflags_root using page_check_range. We would then snapshot only the memory ranges that overlapped between proc self and pageflags_root. However, if a range from proc self maps couldn't be located in pageflags_root, such as when an interval in pageflags_root was merged into a larger one in proc self maps, it would be skipped and not included in the snapshot. This omission led to bugs in the long run.
Now, during snapshotting (pub fn snapshot), we traverse only the pageflags_root tree. We use its intervals to query the proc self maps to gather additional information such as privileges, offset, path, etc. This approach ensures that we capture all memory segments of the emulated target, preventing any segments from being missed.
During the snapshot process, we used to traverse the
proc selftree and match its intervals with those inpageflags_rootusingpage_check_range. We would then snapshot only the memory ranges that overlapped betweenproc selfandpageflags_root. However, if a range fromproc self mapscouldn't be located inpageflags_root, such as when an interval inpageflags_rootwas merged into a larger one inproc self maps, it would be skipped and not included in the snapshot. This omission led to bugs in the long run.Now, during snapshotting (
pub fn snapshot), we traverse only thepageflags_roottree. We use its intervals to query theproc self mapsto gather additional information such as privileges, offset, path, etc. This approach ensures that we capture all memory segments of the emulated target, preventing any segments from being missed.