Maxine Virtual Machine

Architecture

The Maxine VM is characterized internally by aggressive use of advanced language features in Java 1.5 and 1.6, by modular subsystems coordinated through Java interfaces, by the absence of an interpreter, and by a tightly coupled debugger and visualization tool for VM development.

Compatibility

Maxine is plug compatible with an unmodified Java Development Kit (JDK). Maxine can be developed, built, and run in standard Java integrated development environments (IDEs), including NetBeans, Eclipse, and IntelliJ IDEA.

Systems programming in Java

A secondary goal of the project is to develop methods and tools for "systems programming in Java". Compiler extensions, configured in VM source code using Java annotations, allow use, with no performance penalty, of low-level operations otherwise disallowed in Java. These extensions provided the foundation for the Graal compiler.

The Maxine Inspector

Specialized debugging support for the Maxine VM is provided by the Maxine Inspector: a companion tool that acts as a combined object, class, and method browser, and as a machine- and bytecode-level debugger. The Inspector runs out-of-process, needs no active VM support, and leverages code shared with the VM for specialized developer services that exploit detailed knowledge of memory layout and VM design. Notable services include:

• multiple mode views of code (source, bytecode, disassembled machine code) with multi-mode breakpoints and stepping;
• thread, stack, register, and thread local variable inspection;
• flexible low-level memory visualization with dynamic interpretation and linking of memory values, e.g. as code locations, object references;
• dynamic visualization of object fields and metadata;
• boot image configuration details; and
• specialized algorithm-specific support for debugging during GC.

History

Maxine was created by Bernd Mathiske at Sun Labs in early 2005. He led its development among a growing team until late 2008 when he left Sun Microsystems and handed the project over to Doug Simon who had been the first engineer to join it. Doug Simon continued in this role throughout the acquisition of Sun by Oracle Corporation.

The static (heap inspection) version of the Maxine Inspector was created by Bernd Mathiske in 2006. Michael Van De Vanter assumed development of the Inspector in 2007, adding dynamic support as the VM became executable and continued to evolve throughout the acquisition of Sun by Oracle Corporation.

Oracle continued development of Maxine until the release of Maxine 2.0. The University of Manchester is developing Maxine as of release 2.1.

References

Notes

Bibliography

• {{cite conference |last1=Kotselidis |first1=Christos |book-title=Proceedings of the 13th ACM SIGPLAN/SIGOPS International Conference on Virtual Execution Environments
• {{cite journal |last1=Wimmer |first1=Christian |doi-access=free

References

1. (18 November 2021). "Maxine VM: A Metacircular VM for Java in Java".
2. "Oracle Labs – About".
3. "The Maxine Project: The Maxine Inspector".
4. (5 April 2010). "Introduction to the Maxine Inspector (Demo)".
5. (28 August 2010). "Maxine Inspector Mini-Demo 6 of 10 (2008): Multi-code Method Views".
6. (28 August 2010). "Maxine Inspector Mini-Demo 5 of 10 (2008): Disassembled Bytecode".
7. (28 August 2010). "Maxine Inspector Mini-Demo 4 of 10 (2008): Disassembled Machine Code".
8. (28 August 2010). "Maxine Inspector Mini-Demo 10 of 10 (2008): Breakpoints".
9. (28 August 2010). "Maxine Inspector Mini-Demo 7 of 10 (2008): Threads".
10. (28 August 2010). "Maxine Inspector Mini-Demo 9 of 10 (2008): Stacks".
11. (28 August 2010). "Maxine Inspector Mini-Demo 8 of 10 (2008): Registers".
12. (28 August 2010). "Maxine Inspector Mini-Demo 2 of 10 (2008): Memory".
13. (28 August 2010). "Maxine Inspector Mini-Demo 3 of 10 (2008): Heap Objects".
14. (28 August 2010). "Maxine Inspector Mini-Demo 1 of 10 (2008): Boot Image Configuration".
15. "Archived copy".
16. (21 June 2017). "Maxine-VM: Maxine VM: A meta-circular research VM". GitHub.