2e0f753e6f
save cpu->jmp_env in saving context, so uc_emu_start() can be reentrant. also improved Python binding on handling context
2020-06-05 20:12:44 +08:00
540c893157
cleanup qemu/cpus.c
2019-07-31 15:43:06 +08:00
52cb0ba78e
cleanup more synchronization code
2017-01-09 14:05:39 +08:00
fccbcfd4c2
revert to use of g_free to make future qemu integrations easier ( #695 )
...
* revert to use of g_free to make future qemu integrations easier
* bracing
2016-12-21 22:28:36 +08:00
e46545f722
remove glib dependency by provide compatible replacements
2016-12-18 14:56:58 -08:00
cb615fdba7
remove uc->cpus
2016-09-23 07:38:21 -07:00
f99030179c
fix free() -> g_free()
2016-08-11 07:49:19 -07:00
ada1c13662
Fix memleak: do not re-initialize halt_cond
2016-07-06 01:49:10 -05:00
3a742fb6f6
fix conflicts when merging no-thread to master
2016-04-23 10:06:57 +08:00
9467254fc0
strip out per cpu thread code
2016-03-25 17:24:28 -07:00
f0af8f8282
execute cpus in same thread as uc_emu_start()
...
note: I'm sure this makes some dead code
2016-03-23 22:50:56 -07:00
20b01a6933
fix merge conflict
2016-02-01 12:08:38 +08:00
e750a4e97c
when uc_mem_exec() remove EXE permission, quit current TB & continue emulating with TB flushed. this fixes issue in PR #378
2016-01-28 00:56:55 +08:00
580bc7b56a
cleanup
2016-01-10 23:10:00 +08:00
036763d6ae
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.
2016-01-08 01:42:56 +02:00
2f297bdd3a
handle some errors properly so avoid exit() during initialization. this fixes issue #237
2015-11-12 01:43:41 +08:00
8b39ec5b0c
initial support to remove a static variable in qemu-thread-win32.c
2015-09-02 16:13:12 +08:00
344d016104
import
2015-08-21 15:04:50 +08:00
