Bug 34953 - Runtime workbench launch fails silently with JVM 1.4.1 on RC2
Summary: Runtime workbench launch fails silently with JVM 1.4.1 on RC2
Status: RESOLVED DUPLICATE of bug 34808
Alias: None
Product: PDE
Classification: Eclipse Project
Component: Build (show other bugs)
Version: 2.1   Edit
Hardware: Macintosh Mac OS X - Carbon (unsup.)
: P3 critical (vote)
Target Milestone: ---   Edit
Assignee: PDE-Core-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-03-13 14:41 EST by Patrick Anderson CLA
Modified: 2003-03-14 13:19 EST (History)
1 user (show)

See Also:


Attachments
System crash log associated with launcher failure. (6.96 KB, text/plain)
2003-03-13 14:43 EST, Patrick Anderson CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Patrick Anderson CLA 2003-03-13 14:41:25 EST
Using the recently released offical 1.4.1 JVM on MacOS X (10.2.4) with RC2,
the launcher fails silently sometime after the new JVM is started and the
workbench shell appears.  No menu is visible and the application won't 
accept focus.  I'm using a platform version of RC2 to host my feature and 
plugins, and the "Run-time workbench" run configuration type.  I have 
that platform installation of RC2 setup under the 
"Plug-in Development->Target Platform" PDE settings as the external 
plugins location.

Initially, I was using the wrong identifier as the application name in 
the "Run..." dialog, which caused the JVM to terminate silently before 
the workbench window would appear.  Using the correct value simply causes
the workbench to appear for a short time and then disappear, still with 
no indication as to why.

Looking in the system logs, I do get a crash log for "Main", which I will 
attach to this bug.
Comment 1 Patrick Anderson CLA 2003-03-13 14:43:45 EST
Created attachment 4115 [details]
System crash log associated with launcher failure.

This is the crash log for the launch attempt.
Comment 2 DJ Houghton CLA 2003-03-13 16:03:11 EST

*** This bug has been marked as a duplicate of 34808 ***