BJ> I can attest that MEX is blowing up on my intel 
 BJ> based linux system.  :(  Guess I'm going to have to 
 BJ> figure out how to use the debugger tools under my 
 BJ> Linux setup.  I liked the GUI interface NeXTStep / 
 BJ> OpenStep had with the GNU compiler and 
 BJ> debugger.....  That was very nice.....  Back to 
 BJ> using regular (command line driven) GDB if I don't 
 BJ> spot something for the KDE or GNOME desktop 
 BJ> environments.....
 
The good news is that MEX VM seems to be blowing up in a little more sane
manner under Sparc (and probably intel) than it was on Alpha. This suggests
that my first guess (pointer -> int -> pointer) is still a problem,
but that there's another problem, too.
 
Another idea which had crossed my mind would be to replace Scott's heap
allocator entirely; either with straight malloc, an mmap-style allocator,
or maybe Apache Runtime pools (or maybe jabber pools), depending exactly
what the heap semantic is (haven't looked at it closely).
 
As for debuggers, if you want a GUI then ddd is the way to go. It's a
wrapper for gdb (make sure you running gdb 5+), and is quite powerful and
easy to use.
 
Wes

--- Maximus/2 3.01