i want to know that how the information generated by debug build of CLDC software is useful? I want to say that what kind of information can be gathered from that, and how?
Debug build is useful if you need to diagnose internal CLDC VM problems.
It contains debug assertions and additional runtime tracing and debugging options.
But I wanted to know how to diagnose those internal CLDC VM problems, the debug assertions it contains, additional runtime tracing and debugging options.
Can you plz tell me the procedure to extract all that information? Thanks in advance.
Debug assertions fail and crash the VM when some internal VM problem is detected.
You typically should not do anything with assertions unless you see an assertion failure.
For the runtime options you can get the full list by running the debug VM build with -flags argument in the command line. All listed flags are available in debug build.
For the description of flags, you can look in the file src/vm/share/utilities/Globals.hpp in the CLDC source tree. The file starts with a general description of run-time switches framework and then go definitions of run-time flags.
Your use of this web site or any of its content or software indicates your agreement to be bound by these Terms of Participation.
Copyright © 2015, Oracle and/or its affiliates. All rights reserved. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.