File: 13_malloc_test.patch

package info (click to toggle)
db5.3 5.3.28%2Bdfsg1-0.5
  • links: PTS, VCS
  • area: main
  • in suites: buster
  • size: 158,360 kB
  • sloc: ansic: 448,411; java: 111,824; tcl: 80,544; sh: 44,326; cs: 33,697; cpp: 21,604; perl: 14,557; xml: 10,799; makefile: 4,077; yacc: 1,003; awk: 965; sql: 801; erlang: 342; python: 216; php: 24; asm: 14
file content (21 lines) | stat: -rw-r--r-- 677 bytes parent folder | download | duplicates (7)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
--- test/malloc.test
+++ test/malloc.test
@@ -713,17 +713,17 @@
 
 # After committing a transaction in persistent-journal mode, if a journal
 # size limit is configured SQLite may attempt to truncate the journal file.
 # This test verifies the libraries response to a malloc() failure during
 # this operation.
 #
 do_malloc_test 31 -sqlprep {
   PRAGMA journal_mode = persist;
-  PRAGMA journal_size_limit = 1024;
+  PRAGMA journal_size_limit = 8192;
   CREATE TABLE t1(a PRIMARY KEY, b);
 } -sqlbody {
   INSERT INTO t1 VALUES(1, 2);
 }
 
 # When written, this test provoked an obscure change-counter bug.
 # 
 # If, when running in exclusive mode, a malloc() failure occurs