FAQ-O-Matic: Trying to debug a Visibroker project with JB3.5 works, but with JB4.0 it crashes at the first CORBA call with "JVMD_INTERNAL_ERROR". How do I fix this?

	FAQ-O-Matic : General : Debugger : Trying to debug a Visibroker project with JB3.5 works, but with JB4.0 it crashes at the first CORBA call with "JVMD_INTERNAL_ERROR". How do I fix this?
	This is another symptom of the JDK 1.3 HotSpot debugger bugs. Add -classic to the project's VM Parameters to disable HotSpot. 2001-Apr-20 11:25am gyles19@visi.com
	[Append to This Answer]
	2001-Apr-20 11:25am

Previous:	JBuilder's debugger runs horribly slow. How can I speed it up?
Next:	Can't load "jdwp.dll", because Can't find dependent libraries

This document is: http://www.visi.com/~gyles19/cgi-bin/fom.cgi?file=133

	[Search]	[Appearance]
This is a Faq-O-Matic 2.709.

This FAQ administered by gyles19@visi.com.

Other JBuilder Links

Java Community
Java Tools

Code Central
JB OpenTools

Community
Recent
Threads

Borland Chat
Chat FAQ

Feature Matrices
3.0 | 3.5 | 4.0
5.0 | 6.0 | 7.0

Shop for
JBuilder

JBuilder
Downloads
and reg keys

Online Manuals
4.0 | 5.0 | 6.0
7.0

Borland
DevSupport's
Bug/RFE Form
Quality Central Client

JB Patches &
Updates

JBuilder FAQs TIs

JBuilder
Newsgroups

Tamaracka's
News Archive

Mr. Haki's
JBuilder Machine

JGuru's
JBuilder FAQ

Sun's Bug
Parade

Netring

Home - About - Privacy

The Borland JBuilder Netring	by JBuilder FAQ-O-Matic

[ Join Now \| List Sites \| Random \| << Prev \| Next >> ] [ Previous 5 Sites \| Skip Previous \| Skip Next \| Next 5 Sites ]