Fix memory leaks as reported by DrMemory and Valgrind.
ARM and probably the rest of the arches have significant memory leaks as they have no release interface. Additionally, DrMemory does not have 64-bit support and thus I can't test the 64-bit version under Windows. Under Linux valgrind supports both 32-bit and 64-bit but there are different macros and code for Linux and Windows.
This commit is contained in:
@ -2414,7 +2414,6 @@
|
||||
#define qemu_clock_get_us qemu_clock_get_us_arm
|
||||
#define qemu_clock_ptr qemu_clock_ptr_arm
|
||||
#define qemu_clocks qemu_clocks_arm
|
||||
#define qemu_cond_destroy qemu_cond_destroy_arm
|
||||
#define qemu_cpu_is_self qemu_cpu_is_self_arm
|
||||
#define qemu_cpu_kick_thread qemu_cpu_kick_thread_arm
|
||||
#define qemu_daemon qemu_daemon_arm
|
||||
@ -2442,7 +2441,6 @@
|
||||
#define qemu_log_flush qemu_log_flush_arm
|
||||
#define qemu_loglevel_mask qemu_loglevel_mask_arm
|
||||
#define qemu_log_vprintf qemu_log_vprintf_arm
|
||||
#define qemu_mutex_destroy qemu_mutex_destroy_arm
|
||||
#define qemu_mutex_lock_ramlist qemu_mutex_lock_ramlist_arm
|
||||
#define qemu_mutex_trylock qemu_mutex_trylock_arm
|
||||
#define qemu_mutex_unlock_ramlist qemu_mutex_unlock_ramlist_arm
|
||||
|
Reference in New Issue
Block a user