Re: problem with sablevm-1.1.9 xscale

On Tue, Feb 15, 2005 at 11:44:12AM +0000, Asutosh Gopinath wrote:
> > 
> > Hi,
> > 1. 
> > SimpleWrite used to work fine with 1.1.6 but in new release there appears to 
> be 
> > a deadlock
> > 
> > /usr/local/bin/sablevm  SimpleWrite
> > 
> > Devel Library
> > =========================================
> > Native lib Version = RXTX-2.1-7pre17
> > Java lib Version   = RXTX-2.1-7pre17
> > 
> > .... hangs
> > 
> 
> 
> Asutosh Gopinath <asutosh.gopinath <at> lycos.com> writes:
> 
> hi,
> 
> I get following error when i run SimpleWrite under gdb
> 
> 
> The SableVM web site is located at http://www.sablevm.org/ .
> 
> 
> Program received signal SIGSEGV, Segmentation fault.
> _svmf_interpreter (_env=0x0) at interpreter.c:258
> 258     interpreter.c: No such file or directory.
>         in interpreter.c
> (gdb) bt
> #0  _svmf_interpreter (_env=0x0) at interpreter.c:258
> (gdb)
> 
> 
> What does this mean? Help please.
> 
> SableVM version 1.1.9
> - compile date and time: 2005-02-15 22:01:38 UTC
> - gcc version: 3.3.1
> - 'real life brokenness' features enabled
> - signal based exception detection
> - copying garbage collection
> - bidirectional object layout
> - direct-threaded interpreter
> 

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