Как декомпилировать rom.classes

Question

zerbino @zerbino

Java

Как декомпилировать rom.classes

Приветствую! Вытащил из компьютера с QNX файл jxe. Под Java(TM) 2 Runtime Environment, Standard Edition / 1.5.0_11-b03 я так понимаю под SH4. Как просмотреть содержимое rom.classes в удобоваримом виде на ПК кроме как в WinHEX? Первые 4 байта файла «J99J». IDA Pro Advanced не справляется.

Конфиг, запускающий это всё выглядит так:

конфиг

#!/bin/ksh

## Java path setup:
export JAVA_HOME=/j9
export PATH=$JAVA_HOME/bin:$PATH

## TODO: is TIMELOGGER really needed?
## Benchmark time logger:
TIMELOGGER=/usr/apps/bench/TimeLogger

##
## JVM general setup:
##

VMOPTIONS="$VMOPTIONS -Djdsi.trialtimeout=50000"

## Setup library paths for Java generally, J9 and system:
export LD_LIBRARY_PATH=.:/proc/boot:/lib:/lib/dll:/usr/lib:/usr/lib/dll:$JAVA_HOME/bin:/lsd
export EMP_PARAMS=«xres=800,yres=480,disp=lvds,head=1,edid=/lsd/audi800x480_B2.edid»

VMOPTIONS="$VMOPTIONS -Djava.library.path=$LD_LIBRARY_PATH"
VMOPTIONS="$VMOPTIONS -Dcom.ibm.oti.vm.bootstrap.library.path=$LD_LIBRARY_PATH"

## JVM memory management parameters:
VMOPTIONS="$VMOPTIONS -Xmca8k -Xmco8k -Xmo11264k -Xmoi0 -Xmn512k -Xmx13312k"

## Limit Jit memory usage
VMOPTIONS="$VMOPTIONS -Xjit:code=512 -Xjit:codeTotal=2048"

##
## HMI framework setup:
##

## enable use of Iconextractor DSI
VMOPTIONS="$VMOPTIONS -DUseIconExtractor=true"

## configure Benchmark logging to slog
VMOPTIONS="$VMOPTIONS -DSLOG=Ext.Benchmark=0"

## disable trace client connection
#
# depending on trace scope setting the trace client connection can have a severe performance impact
# for all profiling activities, the trace client connection should be disabled

# use this option only for non-asia variants
VMOPTIONS="$VMOPTIONS -DNoTraceClient"

##
## JDSI specific settings:
##

VMOPTIONS="$VMOPTIONS -Djdsi.3SoftOSGi=true"
VMOPTIONS="$VMOPTIONS -Djdsi.noDispatcher"
VMOPTIONS="$VMOPTIONS -Djdsi.trialcount=2000"
VMOPTIONS="$VMOPTIONS -Ddsi.debuglevel=2"
VMOPTIONS="$VMOPTIONS -Ddsi.channel.priority=+1"
VMOPTIONS="$VMOPTIONS -Ddsi.decoder.priority=+1"
VMOPTIONS="$VMOPTIONS -Ddsi.maxPacketLength=16384"
VMOPTIONS="$VMOPTIONS -Ddsi.channel=msgpassing"
VMOPTIONS="$VMOPTIONS -Ddsi.memmode=nopooling"

##
## Graphic adapter specific setup:
##
VMOPTIONS="$VMOPTIONS -Dshowcombi=true"

##
## Green engineering screens setup:
##

## definition directory for green engineering screens:
VMOPTIONS="$VMOPTIONS -Dde.audi.tghu.engineering.base_dir=/HBpersistence/engdefs"

## images reside in file-system
VMOPTIONS="$VMOPTIONS -DImageRoot=/lsd/images"

##
## Setup boot class path / conditionally include TestServer and DSITracer:
##
BOOTCLASSPATH=-Xbootclasspath
MODULAR=no

DSITRACER=/lsd/DSITracer.jar
if [ -f "$DSITRACER" ]; then
BOOTCLASSPATH="$BOOTCLASSPATH:$DSITRACER"
MODULAR=yes
fi

GEM=/lsd/AppDevelopment.jar
if [ -f "$GEM" ]; then
BOOTCLASSPATH="$BOOTCLASSPATH:$GEM"
fi

TEXT=/lsd/texts.jar
if [ -f "$TEXT" ]; then
BOOTCLASSPATH="$BOOTCLASSPATH:$TEXT"
fi

BOOTCLASSPATH="$BOOTCLASSPATH:/lsd/lsd.jxe"

##
## Launch J9
##

## TODO: is TIMELOGGER really needed?
$TIMELOGGER «Before J9 start»

## start j9 in background to finish ksh process.
## if the ksh is left running, this seems to cause some memory management trouble in QNX

if [ $MODULAR = no ]; then
j9 $VMOPTIONS $BOOTCLASSPATH -jxe /lsd/lsd.jxe &
else
echo «WARNING: NON PERFORMANT MODULAR STARTUP!!!»
j9 $VMOPTIONS $BOOTCLASSPATH de.dreisoft.lsd.LSD &
fi