Hello all,

I've undertaken to start a Cygwin port of MUMPSV1, in hopes that the community could benefit from a FOSS, non-InterSystems M implementation on Windows.

First problem I came across was that shmat() on Cygwin (32-bit) doesn't seem to like the 1GB address for SYSTAB_BASE. Instead of giving you a pointer to 0x40000000 as requested, it gives you a pointer to 0x7FD70000. I tried as an experiment defining SYSTAB_BASE as 0x7FD70000, which at least allows the database to be created and the environment to be initialized. However, something goes awry at this point:



So, no globals are getting stored. Go back into the environment, and the following happens:



There's also a MUMPS_CRASH file:



What I'm wondering is if someone has any ideas of what else to try. I'm guessing (somewhat blindly) that I need a better understanding of the "magic" behind SYSTAB_BASE.

Thanks much!

I don't think it's a SYSTAB problem as SYSTAB used to be defined as follows:
#define SYSTAB_BASE (void *)0x1000000 // Base systab for linux

Having said that, I am getting the exact same set of problems trying to port MUMPS to the Raspberry Pi. I changed SYSTAB to the above and am now looking for the other problem which is in the code:

file_off = lseek( dbfd, file_off, SEEK_SET); // Seek to block

I'll let you know when I find the problem.

Ray

The problem was in the packing of structures that described on-disk data.
Now fixed - it would be worth trying the Cygwin port again.

Ray

Thank you sir! I will look into the Cygwin port again once I get out from under some time-critical projects.