mirror of
https://github.com/dingusdev/dingusppc.git
synced 2025-01-13 18:30:44 +00:00
911acb4bc2
It might not be an error - usually it just means that it was already allocated so demote this message to a warning. Related memory allocation changes: - Added find_range_exact which searches for an allocation that exactly matches a range. - Added find_range_contains which searches for an allocation that is completely contained within a range. - Added find_range_overlaps which searches for an allocation that overlaps any part of a range. - Added is_range_free which is similar to the above three. It returns false if any allocated range overlaps a range. It reports the regions that it overlaps. - Fix add_mem_region and add_memio_region so that they don't just check the first byte and last byte. - Memory allocation logging should include the range (first byte..last byte) and device if possible. - Log memory allocations.