libgst: Do not flush cache when creating a new call-in process

The code is already flushing the code on adding a new method _and_
MethodDictionary>>#at:put: and there should be noting in the process
creation that changes the MethodDictionary.

2013-12-22  Holger Hans Peter Freyther  <holger@moiji-mobile.com>

	* interp.c: Do not flush the cache when creating a new
	process.
libgst: Do not flush the cache twice when adding a new method

install_method was flushing the cache twice. Once by calling
>>#at:put: on the MethodDictionary and once by install_method
itself. Only do that when the kernel is not initialized yet.

2013-12-22  Holger Hans Peter Freyther  <holger@moiji-mobile.com>

	* comp.c: Only flush the cache once when adding a new
	CompiledMethod.
libgst: Do not make a suspended process runnable again.

This could be triggered with with the JIT and a simple test case
like this:

  p := [3 factorial] newProcess.
  p singleStep. p suspend.
  self assert: p isSuspended

2014-01-09  Holger Hans Peter Freyther  <holger@moiji-mobile.com>

	* interp.c: Check if the process is already suspended.
libgst: Fix the indication of VMpr_Process_singleStepWaitingOn

The primitive can fail and this is fixing the >>#testStepTooMuch
DebugTools testcase error.

2014-01-09  Holger Hans Peter Freyther  <holger@moiji-mobile.com>

	* prims.def: Mark VMpr_Process_singleStepWaitingOn as
	potentially failing.