Searched refs:stack (Results 1 – 25 of 29) sorted by relevance
12
143 proc trim_frames {stack} { argument144 while {[info exists ::O(ignore.[lindex $stack 0])]} {145 set stack [lrange $stack 1 end]147 return $stack158 trim_frames(lrange(lstack, 0, $ii)) AS stack161 GROUP BY stack162 HAVING stack != ''164 set parent_id [lrange $stack 0 end-1]165 set frame [lindex $stack end]171 $::O(tree) insert $parent_id end -id $stack -text $line -values $v
13 # Ticket #2767 is for a VDBE stack overflow on BEFORE54 # DELETE trigger 32 times, which should overflow the VDBE stack if66 # UPDATE trigger 32 times, which should overflow the VDBE stack if
27 # content of the zeroblob is never instantiated on the VDBE stack.76 # of the blob content occurs on the stack.96 # no instantiation of the zeroblobs occurs on the stack.
184 # Ticket #565. A stack overflow is occurring when the subquery to the302 # Ticket #640: vdbe stack overflow with a LIMIT clause on a SELECT inside338 # Ticket #668: VDBE stack overflow occurs when the left-hand side
110 # extra value on the VDBE stack. This is confusing the parent and114 # Update: Any query with (LIMIT 0) was leaking stack.
40 # not cause processor stack overflow.
362 lappend ::fuzzyopts(-errorlist) {parser stack overflow}
37 generic_unregister stack
571 # Overflow the lemon parser stack by providing an overly complex586 } {1 {parser stack overflow}}588 # Parser stack overflow is silently ignored when it occurs while parsing the
710 # queries causes a parser stack overflow. 718 } "1 {parser stack overflow}"
276 # following query was leaking a couple of stack entries. This query
379 # Ticket #513. Make sure the VDBE stack does not grow on a 3-way join.
339 # Test to make sure a lot of IGNOREs don't cause a stack overflow
345 # Test to make sure a lot of IGNOREs don't cause a stack overflow
374 # Fails under -fsanitize=address,undefined due to stack overflow
1002 # Check for a VDBE stack growth problem that existed at one point.
2975 # switch, then the library uses considerably more stack space than usual.2976 # So much more, that some of the following tests cause stack overflows
623 if(err.stack){624 result.stack = ('string'===typeof err.stack)625 ? err.stack.split(/\n\s*/) : err.stack;
152 const stack = wasm.pstack.pointer;175 wasm.pstack.restore(stack);606 const stack = wasm.pstack.pointer;614 wasm.pstack.restore(stack);774 const stack = wasm.scopedAllocPush();845 wasm.scopedAllocPop(stack);1227 const stack = wasm.scopedAllocPush();1235 wasm.scopedAllocPop(stack);1297 const stack = wasm.scopedAllocPush();1304 wasm.scopedAllocPop(stack);
646 const stack = pstack.pointer,671 pstack.restore(stack);676 const stack = pstack.pointer;687 pstack.restore(stack);691 const stack = pstack.pointer;701 pstack.restore(stack);
1170 const stack = wasm.pstack.pointer; constant1188 wasm.pstack.restore(stack);1316 const stack = wasm.pstack.pointer;1343 wasm.pstack.restore(stack);
61 stack: v.stack, property1032 const stack = P.pointer;1046 .assert(24 === stack - p2)1050 T.assert(p3 === stack-remaining)1053 P.restore(stack);1056 T.assert(P.pointer === stack);1065 P.restore(stack);1068 T.assert(P.pointer === stack);1082 P.restore(stack);1111 wasm.pstack.restore(stack);[all …]
120 const stack = wasm.scopedAllocPush();265 wasm.scopedAllocPop(stack);492 const stack = wasm.scopedAllocPush();505 wasm.scopedAllocPop(stack);
180 REM the current directory on the directory stack.754 REM NOTE: Restore the saved current directory from the directory stack.
410 } {1 {fts5: parser stack overflow}}