If any error occurs during sqlite3_open(), move the database handle into "sick" state. When in the sick state the user can use sqlite3_errcode() and sqlite3_errmsg(), but not much else. (CVS 5628)
FossilOrigin-Name: ce9c74eaab459ddde213c828e821940f5d6cb354
diff --git a/test/malloc.test b/test/malloc.test
index d902a50..542c564 100644
--- a/test/malloc.test
+++ b/test/malloc.test
@@ -16,7 +16,7 @@
# to see what happens in the library if a malloc were to really fail
# due to an out-of-memory situation.
#
-# $Id: malloc.test,v 1.63 2008/07/07 14:56:57 danielk1977 Exp $
+# $Id: malloc.test,v 1.64 2008/08/27 19:01:58 danielk1977 Exp $
set testdir [file dirname $argv0]
source $testdir/tester.tcl
@@ -409,6 +409,9 @@
if {[sqlite3_errcode $DB2] eq "SQLITE_IOERR+12"} {
error "out of memory"
}
+ if {[regexp ".*automatic extension loading.*" [sqlite3_errmsg $DB2]]} {
+ error "out of memory"
+ }
if {$rc} {
error [string range $msg 4 end]
}