From 6043947eee46fdbd63bfede74bc969ad6ea22c30 Mon Sep 17 00:00:00 2001 From: stephan Date: Thu, 24 Aug 2023 14:17:30 +0000 Subject: Ensure that db mutex is held when using sqlite3ErrorWithMessage() to avoid a potential assertion in debug builds. FossilOrigin-Name: b8f6a50a4bf9478324f0272d79f2fe6992a49b753e79e39a268c6afb261bb01e --- ext/wasm/api/sqlite3-wasm.c | 2 ++ 1 file changed, 2 insertions(+) (limited to 'ext/wasm/api/sqlite3-wasm.c') diff --git a/ext/wasm/api/sqlite3-wasm.c b/ext/wasm/api/sqlite3-wasm.c index fcfbc0692..ff15e3b4f 100644 --- a/ext/wasm/api/sqlite3-wasm.c +++ b/ext/wasm/api/sqlite3-wasm.c @@ -352,7 +352,9 @@ int sqlite3_wasm_db_error(sqlite3*db, int err_code, const char *zMsg){ if( db!=0 ){ if( 0!=zMsg ){ const int nMsg = sqlite3Strlen30(zMsg); + sqlite3_mutex_enter(sqlite3_db_mutex(db)); sqlite3ErrorWithMsg(db, err_code, "%.*s", nMsg, zMsg); + sqlite3_mutex_leave(sqlite3_db_mutex(db)); }else{ sqlite3ErrorWithMsg(db, err_code, NULL); } -- cgit v1.2.3