Crashes on first call to uc_xxx

[Nuxar1]

0xC0000005: Access violation writing location 0x000001EF93F60000.

uc_init_engine->machine_initialize->tcg_exec_init->tcg_prologue_init->tcg_target_qemu_prologue->tcg_out_push->tcg_out8

*s->code_ptr++ = v;

with the code

	uc_err err;
	if ((err = uc_open(UC_ARCH_X86, UC_MODE_64, &uc)) != UC_ERR_OK) {
		printf("Failed to initialize unicorn engine: %s\n", uc_strerror(err));
		return;
	}

	if ((err = uc_hook_add(uc, &mem_hook, UC_HOOK_MEM_READ, (void*)mem_hook_callback, this, 1, 0)) != UC_ERR_OK) {
		printf("Failed to add memory hook: %s\n", uc_strerror(err));
		return;
	}

[wtdcode]

#1841

…

________________________________ From: Nuxar1 ***@***.***> Sent: Friday, December 6, 2024 5:10:42 AM To: unicorn-engine/unicorn ***@***.***> Cc: Subscribed ***@***.***> Subject: [unicorn-engine/unicorn] Crashes on first call to uc_xxx (Issue #2062) 0xC0000005: Access violation writing location 0x000001EF93F60000. uc_init_engine->machine_initialize->tcg_exec_init->tcg_prologue_init->tcg_target_qemu_prologue->tcg_out_push->tcg_out8 *s->code_ptr++ = v; with the code uc_err err; if ((err = uc_open(UC_ARCH_X86, UC_MODE_64, &uc)) != UC_ERR_OK) { printf("Failed to initialize unicorn engine: %s\n", uc_strerror(err)); return; } if ((err = uc_hook_add(uc, &mem_hook, UC_HOOK_MEM_READ, (void*)mem_hook_callback, this, 1, 0)) != UC_ERR_OK) { printf("Failed to add memory hook: %s\n", uc_strerror(err)); return; } ― Reply to this email directly, view it on GitHub<#2062>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AHJULOYSX3FGFXLMI4HJJU32EC6NFAVCNFSM6AAAAABTDLJIOWVHI2DSMVQWIX3LMV43ASLTON2WKOZSG4ZDCNBSGY2DSMA>. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[KenionX]

@wtdcode No offence, but how dereferencing a null pointer and causing exceptions is as design? I am also stuck on the old version since this new behavior is just insane to deal with. Even without VS debugger attached it causes crashes from time to time.

[wtdcode]

@wtdcode No offence, but how dereferencing a null pointer and causing exceptions is as design? I am also stuck on the old version since this new behavior is just insane to deal with. Even without VS debugger attached it causes crashes from time to time.

If you read the bug report, the pointer is obviously not null (0x000001EF93F60000).

[wtdcode]

Closing as no activity.

@KenionX submit another issue if you found null pointer dereference.