visualgst: Do not display system exception handling frames in the debugger

Make the debugger skip frames that belong to the system exception
handling. This way a simple '3 halt' will stop in the frame that
signals the exception, e.g. Halt(Exception)>>signal.

In the future a preference will be added to allow to see all the
frames.

2013-06-18  Gwenael Casaccio  <mrgwen@gmail.com>

	* Debugger/Extensions.st: Added.
	* Debugger/GtkDebugger.st: Skip exception handling frames.
	* Extensions.st: Remove the debugger extension.
	* package.xml: Update
jit: Flush the code for the runtime directives

On x86/amd64 this will call mprotect with PROT_EXEC on the
allocated memory. This is fixing an infinite recursion in the
segfault handler of the garbage collection.

2013-06-03  Holger Hans Peter Freyther  <holger@moiji-mobile.com>

	* xlat.c: Use jit_flush_code for the runtime code.
jit: Fix the bootstrap of CharacterArray

CharacterArray>>#withWindowsShellEscapes has the following code
that will lead to execution during the bootstrap. The interpreter
is optimizing the calls for >>#value: but the JIT is not doing that.

Change the order of the bootstrap to load the BlockClosure and
related classes before the CharacterArray.

        table := ##(
            | t |
            t := ByteArray new: 256.
            #($% $" $< $> $| $& $^ $ ) do: [ :each | t at: each codePoint put: 1 ].
            t).

2013-06-03  Holger Hans Peter Freyther  <holger@moiji-mobile.com>

	* files.c: Make BlockClosure available before the CharacterArray.
jit: Fix test failures with Magritte, SUnit and other routines

The tests crash when returning to a previous context. In the case of the
Magritte test it is crashing on return to Delay class>>#runDelayProcess.

This appears to occur when resuming an existing image. It is because
the F_XLAT and F_XLAT_REACHABLE flags are cleared on saving of the image.
On image resume the refresh_native_ips method will re-generate the
native code and set the F_XLAT flag for active contexts. As the native
code is not executed the F_XLAT_REACHABLE will not be set. This makes it
possible for maybe_release_xlat to release the native code without
updating the context. This will eventually cause a segmentation fault
as the native code is gone.

The solution appears to be easy. Once the native_ip is updated the
F_XLAT_REACHABLE is set. This way it is guaranteed that the native code
will not be collected.

2013-06-10  Holger Hans Peter Freyther  <holger@moiji-mobile.com>

	* interp-jit.inl: Set the F_XLAT_REACHABLE flag in refresh_native_ips.