Re: problem with sablevm-1.1.9 xscale

> This segmentation fault is probably normal.  Signal-based exception
> detection is enable and SableVM uses an implicit null pointer check to
> know when it should initialize instructions.
> 
> Disabling signal-based exception or enabling debugging mode (check
> ./configure --help for exact options name) will remove these "normal"
> seg fault.  Alternatively, you could just type "cont" to continue
> normal execution if it is an expected fault.
> 
> Note: Your gdb does not find source files.  I had this issue before with
> some gdb versions.  It will be difficult to debug.
> 
> David
> 
> ---
> 
> David Bélanger
> Web page:   http://www.cs.mcgill.ca/~dbelan2/
> Public key: http://www.cs.mcgill.ca/~dbelan2/public_key.txt
> 


I recompiled it with Disabled signal-based exception 

gdb gives this:

Devel Library
=========================================
Native lib Version = RXTX-2.1-7pre17
Java lib Version   = RXTX-2.1-7pre17

Program received signal SIGSEGV, Segmentation fault.
_svmf_invoke_native_nonstatic (env=0x13d80) at native.c:1432
1432    native.c: No such file or directory.
        in native.c
(gdb) cont
Continuing.

Program terminated with signal SIGSEGV, Segmentation fault.
The program no longer exists.
(gdb) q
============
SableVM version 1.1.9
- compile date and time: 2005-02-16 15:35:34 UTC
- gcc version: 3.3.1
- 'real life brokenness' features enabled
- copying garbage collection
- bidirectional object layout
- direct-threaded interpreter


Asutosh