|
|
|
|
| Re: New versions of DTFJ adapter and DTFJ [message #10751 is a reply to message #10719] |
Sat, 23 May 2009 09:01   |
Eclipse User |
|
|
|
Originally posted by: heinz.drews.gmail.com
> If the file has any of the known extension (like "phd" and "dmp" etc.)
> then the script should recognize the right adapter - and also read
> DTFJ-formatted dumps.
> Let me know if it doesn't work for you (and give me some details to
> start digging into it)!
Hello Andreas,
pointing to a .phd provides me with an exception as shown below.
I assume that I got the installation of DTFJ wrong.
The analysis starts using the RCP but there I got heap problems.
Trying now to find as much memory as possible.
!SESSION 2009-05-23 10:54:59.896
-----------------------------------------------
eclipse.buildId=unknown
java.version=1.6.0_13
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=de_DE
Framework arguments: -application org.eclipse.mat.api.parse
\tmp\heapdump454684.1242303149.phd
Command-line arguments: -os win32 -ws win32 -arch x86 -consoleLog
-application org.eclipse.mat.api.parse \tmp\heapdump454684.1242303149.phd
!ENTRY org.eclipse.mat.parser 4 0 2009-05-23 10:55:01.881
!MESSAGE Error opening heap dump
!SUBENTRY 1 org.eclipse.mat.parser 4 0 2009-05-23 10:55:01.881
!MESSAGE Not a HPROF heap dump
!STACK 0
java.io.IOException: Not a HPROF heap dump
at
org.eclipse.mat.hprof.AbstractParser.readVersion(AbstractPar ser.java:122)
at org.eclipse.mat.hprof.Pass1Parser.read(Pass1Parser.java:69)
at org.eclipse.mat.hprof.HprofIndexBuilder.fill(HprofIndexBuild er.java:65)
at
org.eclipse.mat.parser.internal.SnapshotFactoryImpl.parse(Sn apshotFactoryImpl.java:184)
at
org.eclipse.mat.parser.internal.SnapshotFactoryImpl.openSnap shot(SnapshotFactoryImpl.java:102)
at
org.eclipse.mat.snapshot.SnapshotFactory.openSnapshot(Snapsh otFactory.java:113)
at
org.eclipse.mat.internal.apps.ParseSnapshotApp.parse(ParseSn apshotApp.java:104)
at
org.eclipse.mat.internal.apps.ParseSnapshotApp.start(ParseSn apshotApp.java:93)
at
org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips eAppHandle.java:193)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(EclipseAppLauncher.java:110)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:79)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:386)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java: 549)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
!ENTRY org.eclipse.osgi 4 0 2009-05-23 10:55:01.897
!MESSAGE Application error
!STACK 1
org.eclipse.mat.SnapshotException: Error opening heap dump
'heapdump454684.1242303149.phd'. Check log for details.
at
org.eclipse.mat.parser.internal.SnapshotFactoryImpl.parse(Sn apshotFactoryImpl.java:219)
at
org.eclipse.mat.parser.internal.SnapshotFactoryImpl.openSnap shot(SnapshotFactoryImpl.java:102)
at
org.eclipse.mat.snapshot.SnapshotFactory.openSnapshot(Snapsh otFactory.java:113)
at
org.eclipse.mat.internal.apps.ParseSnapshotApp.parse(ParseSn apshotApp.java:104)
at
org.eclipse.mat.internal.apps.ParseSnapshotApp.start(ParseSn apshotApp.java:93)
at
org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips eAppHandle.java:193)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(EclipseAppLauncher.java:110)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:79)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:386)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java: 549)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
!ENTRY org.eclipse.osgi 2 0 2009-05-23 10:55:01.913
!MESSAGE One or more bundles are not resolved because the following root
constraints are not resolved:
!SUBENTRY 1 org.eclipse.osgi 2 0 2009-05-23 10:55:01.913
!MESSAGE Bundle
update@plugins/org.eclipse.mat.jdt_0.7.100.200905071012.jar was not
resolved.
!SUBENTRY 2 org.eclipse.mat.jdt 2 0 2009-05-23 10:55:01.913
!MESSAGE Missing required bundle org.eclipse.jdt.core_0.0.0.
!SUBENTRY 2 org.eclipse.mat.jdt 2 0 2009-05-23 10:55:01.913
!MESSAGE Missing required bundle org.eclipse.jdt.ui_0.0.0.
!ENTRY org.eclipse.osgi 2 0 2009-05-23 10:55:01.913
!MESSAGE The following is a complete list of bundles which are not
resolved, see the prior log entry for the root cause if it exists:
!SUBENTRY 1 org.eclipse.osgi 2 0 2009-05-23 10:55:01.913
!MESSAGE Bundle
update@plugins/org.eclipse.mat.jdt_0.7.100.200905071012.jar [65] was not
resolved.
!SUBENTRY 2 org.eclipse.mat.jdt 2 0 2009-05-23 10:55:01.913
!MESSAGE Missing required bundle org.eclipse.jdt.ui_0.0.0.
!SUBENTRY 2 org.eclipse.mat.jdt 2 0 2009-05-23 10:55:01.913
!MESSAGE Missing required bundle org.eclipse.jdt.core_0.0.0.
|
|
|
|
| Re: New versions of DTFJ adapter and DTFJ [message #11091 is a reply to message #10782] |
Mon, 25 May 2009 19:03 |
| Eclipse User |
|
|
|
Originally posted by: heinz.drews.gmail.com
Andrew Johnson wrote:
> osgi.bundles=org.eclipse.mat.dtfj@4:start,org.eclipse.equinox.common@2:start,org.eclipse.update.configurator@3:start,org.eclipse.core.runtime@start
>
>
> The reason is because the DTFJ adapter dynamically declares to MAT which
> DTFJ files it supports depending on which DTFJ implementations are
> available in the MAT application. However for this code to run the DTFJ
> adapter must get started. In GUI mode there is an extension point I can
> use to get the DTFJ adapter started. I haven't found a corresponding
> extension point in batch mode. This modification to the osgi.bundles
> statement ensures that the DTFJ adapter is started early and can then
> query the DTFJ implementation and notify MAT which files it supports.
>
> Once the adapter is part of the MAT distribution we might be able to do
> something better.
>
Thanks, the configuration change has helped.
I'm also searching for a solution getting bundles started without
changing the config.ini.
|
|
|
Powered by
FUDForum. Page generated in 0.02951 seconds
] 
Search
Help
Register
Login
Home
