Differences

This shows you the differences between two versions of the page.

--- leuphana:presentation [2013/09/05 10:13]
jj
+++ leuphana:presentation [2013/09/10 08:09] (current)
jj
@@ Line 1: / Line 1: @@
 **Life versus Object. Comrade Things and Alien Life: Stack Frame Heap**
+{{:leuphana:stack.jpeg?300|}}
 {{:leuphana:sfh1.png|}}
@@ Line 18: / Line 20: @@
 Stack, Frame, Heap is a series of interventions within the mined or damaged environment, attempting to impose logical or computational structures on this geological landscape. Re-animating the disjuncture of nature and pysche (animism), selected computational substrates and refining by-products will be re-interred or returned into the earth (in nature), sparse insertions of computationally derived (component, process) products will sited within the landscape (pits, mines, field) and nurtured over time.
-**[what exactly is Stack Heap and Frame? How we go further with these terms?]**
+===== stack/heap/frame in computation=====
+A clearer understanding of stack, heap, frame in terms of computation:
+An idealised stack, heap, frame: http://www.dcs.warwick.ac.uk/research/modelling/other/eden/advanced/notes/stack.html
+Call stack: http://en.wikipedia.org/wiki/Call_stack
+Stack (dynamic process) is made up of stack frames for each subroutine/function call when it is called (so there is really a stack of stack frames). Heap (allotted) is for arrays and static variables. Both are in contiguous memory and the stack can grow down to merge/leak into the heap.
+See also: http://lambda.uta.edu/cse5317/notes/node33.html and:
+http://www.linuxjournal.com/article/6391
+===== How we go further with these terms? =====
 eg. stack protection from stack smashes by stack canaries (mining) - used to detect a stack buffer overflow before execution of malicious code can occur - see howto bypass them eg.http://phrack.org/issues.html?issue=56&id=5 && mushrooms/similar (shellfish) indicators/asorbers of toxins
+Stack overflowing/manipulation and how this can be used to execute malicious code/shift the site of execution. (how?)
+Stack overflow: The most common cause of stack overflow is excessively deep or infinite recursion. (also creating large local variables).
 ====== Why: ======
@@ Line 38: / Line 61: @@
 like), and, further, re-characterizing through practice any discussion of (im)permaculture and technological
 autophagia.
 {{:leuphana:sfh3.gif?600|}}
@@ Line 97: / Line 121: @@
 ====== further ======
-- that this can be defined as some kind of bootstrapping - an
+that this can be defined as some kind of bootstrapping - an imposition on the site and a manipulation of certain favourable conditions
-  imposition on the site and a manipulation of certain favourable
-  conditions
-- and how these changes are rendered visible: plant indicators, a
+and how these changes are rendered visible: plant indicators, a measurement which is part of the earth and becomes an expression acting on itself, some kind of probe/display
-  measurement which is part of the earth and becomes an expression
-  acting on itself, some kind of probe/display
 ====== demonstrations/field notes/experiments ======
+====== misc images ======
+{{:leuphana:stack1.jpeg|}}
+mud computing

jonathan kemp

User Tools

Site Tools

Differences

Page Tools