[go: up one dir, main page]

File: debugging.txt

package info (click to toggle)
sablevm 1.11.3-1
  • links: PTS
  • area: main
  • in suites: sarge
  • size: 6,980 kB
  • ctags: 7,922
  • sloc: ansic: 116,013; sh: 8,679; makefile: 489
file content (30 lines) | stat: -rw-r--r-- 1,508 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
 * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
 * This source file is part of SableVM.                            *
 *                                                                 *
 * See the file "LICENSE" for the copyright information and for    *
 * the terms and conditions for copying, distribution and          *
 * modification of this source file.                               *
 * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

*** SableVM Information about DEBUGGING ***

DEBUGGING VERSION COMPILATION
  --enable-debugging-features - add that option to ./configure call to get
  switched interpreter with all possible checks and verbose options.
  NOTE: This doesn't work with inlined engine (don't force inlined).
  NOTE: Such JVM is much slower than normally.

DEBUGGING PROPERTIES
  sablevm.verbose.methods - when operating on a binary compiled with
  debugging features - setting this property to true outputs names of
  every method that is to be executed.

  sablevm.verbose.instructions - when operating on a binary compiled
  with debugging features - setting this property to  true  outputs
  names of every instruction that is to be executed (WARNING: expect flood!!!)
  NOTE: This requires "debugging features" enabled (See above).

DEBUGGING METHODS
  java.lang.Runtime.traceMethodCalls and java.lang.Runtime.traceInstructions
  help getting smaller traces; you simply modify your program to call these
  methods around the problem spots.