So you have a recursive doesNotUnderstand: error and the system is running
out of memory. The questions are where and why? You can try and debug
this further by running the VM with --trace=259, e.g.
pharo-vm/pharo --trace=259 my image.image
This will produce lots of output, eventually ending in an endless stream of
doesNotUnderstand:'s. So capture the first few megabytes of output (see
e.g. head(1) ($ man head))
FYI
"traceFlags is a set of flags.
1 => print trace (if something below is selected)
2 => trace sends
4 => trace block activations
8 => trace interpreter primitives
16 => trace events (context switches, GCs, etc)
32 => trace stack overflow
64 => send breakpoint on implicit receiver (Newspeak VM only)
128 => check stack depth on send (simulation only)
256 => trace linked sends "
Alternatively you could use a debugger such as gdb and I can tell you how
to put a breakpoint on doesNotUnderstand:
Hi Dario,
Most recent primitives doesNotUnderstand: doesNotUnderstand: doesNotUnderstand: doesNotUnderstand: doesNotUnderstand: doesNotUnderstand: doesNotUnderstand: doesNotUnderstand: doesNotUnderstand: ....... ...... doesNotUnderstand: doesNotUnderstand: doesNotUnderstand: doesNotUnderstand: doesNotUnderstand: doesNotUnderstand: doesNotUnderstand: doesNotUnderstand: doesNotUnderstand: doesNotUnderstand: doesNotUnderstand:
So you have a recursive doesNotUnderstand: error and the system is running out of memory. The questions are where and why? You can try and debug this further by running the VM with --trace=259, e.g.
pharo-vm/pharo --trace=259 my image.image
This will produce lots of output, eventually ending in an endless stream of doesNotUnderstand:'s. So capture the first few megabytes of output (see e.g. head(1) ($ man head))
FYI "traceFlags is a set of flags. 1 => print trace (if something below is selected) 2 => trace sends 4 => trace block activations 8 => trace interpreter primitives 16 => trace events (context switches, GCs, etc) 32 => trace stack overflow 64 => send breakpoint on implicit receiver (Newspeak VM only) 128 => check stack depth on send (simulation only) 256 => trace linked sends "
Alternatively you could use a debugger such as gdb and I can tell you how to put a breakpoint on doesNotUnderstand: