sigsev in 64/32 bit VM
martinkuball at web.de
Mon May 29 19:51:58 UTC 2006
Am Sunday, 28. May 2006 20:54 schrieb David T. Lewis:
> Hi Martin,
> It's been a couple of months since I've tried compiling a VM on
> amd64, but if noone else replies to this I'll give it a try
> sometime in the next couple of days and let you know if it works
> for me. Right now I'm too busy drinking beer and enjoying a long
> Memorial Day weekend ;) (that's the US holiday to honor war
> veterans, but also the semi-official first day of summer).
> In the past I have seen symptoms like this due to problems in the
> memory access macros/functions in sqMemoryAccess.h, but it really
> could be caused by most anything. You should definitely build only
> the absolutely necessary plugins until you get the VM to run, as
> many of the plugins are not 64 bit clean.
What exactly are the absoulutely necessary plugins?
> On Sun, May 28, 2006 at 07:26:11PM +0200, Martin Kuball wrote:
> > Am Sunday, 28. May 2006 15:24 schrieb Martin Kuball:
> > > Hi!
> > >
> > > I compiled a 64/32 bit VM from svn. Immediately after start I
> > > get a SIGSEV at: interp.c line 7865:
> > >
> > > longAtput(where + ((ReceiverIndex + i) << ShiftForWord),
> > > longAtPointer(localSP - ((argCount2 - i) * BytesPerWord)));
> > >
> > > I examined the arguments to longAtput and they seem OK. But
> > > there is no Memory mapped at sqMemoryBase. How could that
> > > happen?
> > >
> > > Martin
> > Forgot to give you some more details. I'm running a amd64 system
> > with linux 2.6.14. Compiler ist gcc 4.0.3.
> > Martin
More information about the Vm-dev