[news.eclipse.tools] Re: Mac OS X?

[john_arthorne@xxxxxxxx (John Arthorne)]

The trace information is printed to the console, not the log file, so what
you're seeing is expected.  Normally you can add a pause at the end of the
script or batch file that launches Eclipse to allow capturing of the
complete log, or else pipe stdout to a file.

I have logged bug #4930 for this problem.  I don't understand the trace,
because 0.75 is the standard load factor for a hash map so I don't see how
it's illegal.  I don't have access to your platform type so it's difficult
to investigate...  Still, thanks for reporting this bug!

Channing Walton wrote:

> Hi,
> I tried what was suggested but nothing was produced in
> workspace/.metadata/.log file, however the dos window that popped up upon
> startup produced the following stack trace (which was hard to grab since the
> window disappears after the exception):

> Boot URL:
>     jar:file:C:/eclipse/plugins/org.eclipse.core.boot/boot.jar!/
> Install URL: file:C:/eclipse/
> Debug-Options: file:C:/eclipse/.options
> RegistryLoader: Parsed Registry: 12678ms [+12678ms]
> Exception launching the Eclipse Platform:
> java.lang.reflect.InvocationTargetException:
> java.lang.reflect.InvocationTargetE
> xception: java.lang.IllegalArgumentException: Illegal Load factor: 0.75
>         at java.util.HashMap.<init>(HashMap.java:142)
>         at java.util.HashMap.<init>(HashMap.java:168)
>         at
> org.eclipse.core.internal.plugins.RegistryResolver.resolve(RegistryRe
> solver.java:684)
>         at
> org.eclipse.core.runtime.model.PluginRegistryModel.resolve(PluginRegi
> stryModel.java:357)
>         at
> org.eclipse.core.internal.runtime.InternalPlatform.loadRegistry(Inter
> nalPlatform.java:617)
>         at
> org.eclipse.core.internal.runtime.InternalPlatform.loaderStartup(Inte
> rnalPlatform.java:526)
>         at java.lang.reflect.Method.invoke(Native Method)
>         at
> org.eclipse.core.internal.boot.InternalBootLoader.startup(InternalBoo
> tLoader.java:912)
>         at
> org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoa
> der.java:803)
>         at org.eclipse.core.boot.BootLoader.run(BootLoader.java:285)
>         at java.lang.reflect.Method.invoke(Native Method)
>         at org.eclipse.core.launcher.Main.basicRun(Main.java:151)
>         at org.eclipse.core.launcher.Main.run(Main.java:433)
>         at org.eclipse.core.launcher.Main.main(Main.java:306)


> --
> ----
> Channing Walton
> http://www.channing.u-net.com
> "DJ Houghton" <dj_houghton@xxxxxxx> wrote in message
> news:9q23ln$knv$1@xxxxxxxxxxxxxxxx
> > To enable the logging of extra debugging information in Eclipse, there are
> 2
> > things that you must do.
> >
> > 1). specify/create a .options file
> > 2). add the "-debug" command line argument when calling eclipse.exe
> >
> > Several plugins contribute a .options file which contains specific
> debugging
> > information for their plugin. Two examples are org.eclipse.core.runtime
> and
> > org.eclipse.core.resources. If desired, you can also combine the contents
> of
> > multiple .options files into one.
> >
> > I would suggest copying the file:
> >     plugins/org.eclipse.core.runtime/.options
> > to be a sibling of the plugins/ directory (e.g. the same directory as the
> > eclipse.exe) and then run using the -debug command line argument.
> >
> > This will generate a lot of information w.r.t. class loading and plugin
> > activation and may be useful in determining where the problem is.
> > Information will be put into the workspace/.metadata/.log file.
> >
> > It would also be helpful if you could post the contents of the log file so
> > we can take a look at it.
> >
> >                       dj
> >
> >
> > "McQ" <mike_wilson@xxxxxxx> wrote in message
> > news:9q1rcc$hkg$1@xxxxxxxxxxxxxxxx
> > > There is a way, but I don't know it. I'll get somebody who does to reply
> > to
> > > the thread.
> > >
> > > McQ.
> > >
> > > "Channing Walton" <channing.walton@xxxxxxxxx> wrote in message
> > > news:9q1aul$ami$1@xxxxxxxxxxxxxxxx
> > > > I'd love to know but no logs are generated :-(
> > > > Are there any logging options I could add to give more info?
> > > >
> > > > Channing
> > > > --
> > > > ----
> > > > Channing Walton
> > > > http://www.channing.u-net.com
> > > > "McQ" <mike_wilson@xxxxxxx> wrote in message
> > > > news:9pvh2a$lbg$1@xxxxxxxxxxxxxxxx
> > > > > If you come to any conclusions as to why we are failing on VPC, I'd
> > love
> > > > to
> > > > > hear them.
> > > > >
> > > > > McQ.
> > > > >
> > > > >
> > > > > "Channing Walton" <channing.walton@xxxxxxxxx> wrote in message
> > > > > news:9nkkrg$un6$1@xxxxxxxxxxxxxxxx
> > > > > > As a matter of interest to those tempted to use Connectix
> VirtualPC
> > on
> > > X
> > > > > to
> > > > > > run Eclipse...don't bother, it won't. I don't know what the error
> is
> > > as
> > > > no
> > > > > > logs are generated. Eclipse gets as far as building the workspace
> > > > > directory
> > > > > > and then exits.
> > > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >