From c95af7c81bd06f4fe241f8c71ffa8ef66e6b5b71 Mon Sep 17 00:00:00 2001 From: ptitSeb Date: Thu, 15 Jul 2021 09:25:01 +0200 Subject: [DYNAREC] Don't limit the retry pattern on access error signal, as it often happens when creating new bridges (might help #57) --- src/libtools/signals.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'src/libtools') diff --git a/src/libtools/signals.c b/src/libtools/signals.c index 86eb75ef..d56e73ee 100755 --- a/src/libtools/signals.c +++ b/src/libtools/signals.c @@ -791,7 +791,7 @@ void my_box64signalhandler(int32_t sig, siginfo_t* info, void * ucntx) static void* glitch_pc = NULL; static void* glitch_addr = NULL; static int glitch_prot = 0; - if(addr && pc && db) { + if(addr && pc /*&& db*/) { if((glitch_pc!=pc || glitch_addr!=addr || glitch_prot!=prot)) { // probably a glitch due to intensive multitask... dynarec_log(/*LOG_DEBUG*/LOG_INFO, "SIGSEGV with Access error on %p for %p, db=%p, prot=0x%x, retrying\n", pc, addr, db, prot); -- cgit 1.4.1