Ziele Untersuchung
mit Columbo Integrität von
Datenbanken Interaktion und
Portierbarkeit Ergonomie der
Schnittstellen

Angebot Produkte Projekt Beratung

Mittel Analytik Modellierung Sprachen Algebra Logik Hardware Denken Kreativität

Zusammenhänge Gesellschaft Wirtschaft Branche Firma

Benutzer


products/Sources/formale Sprachen/C/Android/dalvik/dalvik/docs/ (Android Betriebssystem Version 17^©) Datei vom 26.5.2026 mit Größe 3 kB

Quelle hello-world.html

Sprache: HTML

products/Sources/formale Sprachen/C/Android/dalvik/dalvik/docs/hello-world.html

<html>
<head>
 <title>Basic Dalvik VM Invocation</title>
</head>

<body>
<h1>Basic Dalvik VM Invocation</h1>


On an Android device, the Dalvik virtual machine usually executes embedded
in the Android application framework. It's also possible to run it directly,
just as you would a virtual machine on your desktop system.

After compiling your Java language sources, convert and combine the .class
files into a DEX file, and push that to the device. Here's a simple example:

<code>
% echo 'class Foo {'\ 
> 'public static void main(String[] args) {'\ 
> 'System.out.println("Hello, world"); }}' > Foo.java 
% javac Foo.java 
% dx --dex --output=foo.jar Foo.class 
% adb push foo.jar /sdcard 
% adb shell dalvikvm -cp /sdcard/foo.jar Foo 
Hello, world
</code>

The <code>-cp</code> option sets the classpath. The initial directory
for <code>adb shell</code> may not be what you expect it to be, so it's
usually best to specify absolute pathnames.


The <code>dx</code> command accepts lists of individual class files,
directories, or Jar archives. When the <code>--output</code> filename
ends with <code>.jar</code>, <code>.zip</code>, or <code>.apk</code>,
a file called <code>classes.dex</code> is created and stored inside the
archive.

Run <code>adb shell dalvikvm -help</code> to see a list of command-line
options.


<h2>Using a debugger</h2>


You can debug stand-alone applications with any JDWP-compliant debugger.
There are two basic approaches.

The first way is to connect directly through TCP. Add, to the "dalvikvm"
invocation line above, an argument like:

<code> -agentlib:jdwp=transport=dt_socket,address=8000,server=y,suspend=y</code>

This tells the VM to wait for a debugger to connect to it on TCP port 8000.
You need to tell adb to forward local port 8000 to device port 8000:

<code>% adb forward tcp:8000 tcp:8000</code>

and then connect to it with your favorite debugger (using <code>jdb</code>
as an example here):

<code>% jdb -attach localhost:8000</code>

When the debugger attaches, the VM will be in a suspended state. You can
set breakpoints and then tell it to continue.


You can also connect through DDMS, like you would for an Android application.
Add, to the "dalvikvm" command line:

<code> -agentlib:jdwp=transport=dt_android_adb,suspend=y,server=y</code>

Note the <code>transport</code> has changed, and you no longer need to
specify a TCP port number. When your application starts, it will appear
in DDMS, with "?" as the application name. Select it in DDMS, and connect
to it as usual, e.g.:

<code>% jdb -attach localhost:8700</code>

Because command-line applications don't include the client-side
DDM setup, features like thread monitoring and allocation tracking will not
be available in DDMS. It's strictly a debugger pass-through in this mode.

See <a href="debugger.html">Dalvik Debugger Support</a> for more information
about using debuggers with Dalvik.


<address>Copyright © 2009 The Android Open Source Project</address>

</body>
</html>

Messung V0.5 in Prozent

¤ Dauer der Verarbeitung: 0.10 Sekunden (vorverarbeitet am 2026-06-27) ¤

Wurzel

Suchen

PVS Prover

Isabelle Prover

NIST Cobol Testsuite

Cephes Mathematical Library

Vienna Development Method

Haftungshinweis

Die Informationen auf dieser Webseite wurden nach bestem Wissen sorgfältig zusammengestellt. Es wird jedoch weder Vollständigkeit, noch Richtigkeit, noch Qualität der bereit gestellten Informationen zugesichert.