<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: OpenVMS Java Debugging in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/openvms-java-debugging/m-p/5194282#M42707</link>
    <description>I have the answer from the replies through the forums.</description>
    <pubDate>Thu, 20 Aug 2009 13:29:06 GMT</pubDate>
    <dc:creator>circepb</dc:creator>
    <dc:date>2009-08-20T13:29:06Z</dc:date>
    <item>
      <title>OpenVMS Java Debugging</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/openvms-java-debugging/m-p/5194278#M42703</link>
      <description>Can anyone tell me how to do a java debugging session under OpenVMS? I am using OpenVMS V7.3-2 Java 1.42. I can compile (javac) and run it java "HelloWorld" but don't know how to bring up the debugging session. java_dbg "HelloWorld" does not bring up the java source code from the current directory.&lt;BR /&gt;&lt;BR /&gt;David</description>
      <pubDate>Wed, 19 Aug 2009 17:01:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/openvms-java-debugging/m-p/5194278#M42703</guid>
      <dc:creator>circepb</dc:creator>
      <dc:date>2009-08-19T17:01:56Z</dc:date>
    </item>
    <item>
      <title>Re: OpenVMS Java Debugging</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/openvms-java-debugging/m-p/5194279#M42704</link>
      <description>Do you mean running jdb?&lt;BR /&gt;&lt;BR /&gt;$ @sys$startup:java$142_setup classic&lt;BR /&gt;$ type hello.java&lt;BR /&gt;import java.io.*;&lt;BR /&gt;public class Hello {&lt;BR /&gt;&lt;BR /&gt;  public static void main(String argv[]) {&lt;BR /&gt;    System.out.println("Hello");&lt;BR /&gt;  }&lt;BR /&gt;}&lt;BR /&gt;$ javac -g hello.java&lt;BR /&gt;$ jdb "Hello&lt;BR /&gt;Initializing jdb ...&lt;BR /&gt;&amp;gt; stop in Hello.main&lt;BR /&gt;Deferring breakpoint Hello.main.&lt;BR /&gt;It will be set after the class is loaded.&lt;BR /&gt;&amp;gt; run "Hello&lt;BR /&gt;run  "Hello&lt;BR /&gt;&amp;gt;&lt;BR /&gt;VM Started: Set deferred breakpoint Hello.main&lt;BR /&gt;&lt;BR /&gt;Breakpoint hit: "thread=main", Hello.main(), line=5 bci=0&lt;BR /&gt;5        System.out.println("Hello");&lt;BR /&gt;&lt;BR /&gt;main[1]</description>
      <pubDate>Thu, 20 Aug 2009 07:40:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/openvms-java-debugging/m-p/5194279#M42704</guid>
      <dc:creator>H.Becker</dc:creator>
      <dc:date>2009-08-20T07:40:30Z</dc:date>
    </item>
    <item>
      <title>Re: OpenVMS Java Debugging</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/openvms-java-debugging/m-p/5194280#M42705</link>
      <description>Due to the nature of the beast, Java cannot be debugged using the VMS debugger, which deals with native code only; AFAIK, the VM has no facilities for any other debugger than it's own. So you'll have to rely on the debugger facilities of the VM, and I doubt it would be different than running Java on other platforms.&lt;BR /&gt;The VMS debugger is only feasable if you want to debug the VM itself, which may be possibble if you had the source code, or at least (machine-code) listings and mapfile. But that is, I think, not what you're after.</description>
      <pubDate>Thu, 20 Aug 2009 10:22:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/openvms-java-debugging/m-p/5194280#M42705</guid>
      <dc:creator>Willem Grooters</dc:creator>
      <dc:date>2009-08-20T10:22:47Z</dc:date>
    </item>
    <item>
      <title>Re: OpenVMS Java Debugging</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/openvms-java-debugging/m-p/5194281#M42706</link>
      <description>The OpenVMS debugger (presently?) has no capabilities with interpreted code.  This whether the code is Javac-compiled into JVM byte code interpreter code, JIT code, or a more classic and traditional interpreter.&lt;BR /&gt;&lt;BR /&gt;This means that Java, Ruby, Lua, php, perl, python and the other modern languages are not supported by the OpenVMS debugger.  A few classic languages are also left out here, too.  Well, other than debugging the interpreter itself.</description>
      <pubDate>Thu, 20 Aug 2009 13:23:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/openvms-java-debugging/m-p/5194281#M42706</guid>
      <dc:creator>Hoff</dc:creator>
      <dc:date>2009-08-20T13:23:10Z</dc:date>
    </item>
    <item>
      <title>Re: OpenVMS Java Debugging</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/openvms-java-debugging/m-p/5194282#M42707</link>
      <description>I have the answer from the replies through the forums.</description>
      <pubDate>Thu, 20 Aug 2009 13:29:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/openvms-java-debugging/m-p/5194282#M42707</guid>
      <dc:creator>circepb</dc:creator>
      <dc:date>2009-08-20T13:29:06Z</dc:date>
    </item>
  </channel>
</rss>

