Closed Bug 82729 Opened 25 years ago Closed 25 years ago

Blackconnect should not crash mozilla on improper CLASSPATH

Categories

(Core Graveyard :: Java to XPCOM Bridge, defect, P1)

defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: edburns, Assigned: blackconnect)

Details

(Keywords: crash)

Attachments

(1 file)

I just built blackconnect for the first time, and after I built it I can no longer run mozilla without having my CLASSPATH set to mozilla\dist\classes. It should be the case that mozilla doesn't crash when you have blackconnect installed AND don't have the proper CLASSPATH. Basically what I'm saying is, it should fail gracefully.
Keywords: crash
Agreed. P1
Priority: -- → P1
Does this affect the m.9.1 trunk build?
It does not affect the build. blackConnect is not a part of default build
Status: NEW → ASSIGNED
Attached patch fix for the bugSplinter Review
There are two reasons for the browser to crash: 1. No CLASSPATH at all 2. BlackConnect classes are not in the CLASSPATH Take a look at http://bugzilla.mozilla.org/showattachment.cgi?attach_id=36622 1. No CLASSPATH case served in bcJavaGlobal.cpp. - added checking for CLASSPATH equal to NULL. 2. Improper CLASSPATH case served in - bcJavaStubsAndProxies.cpp added returning NS_ERROR_FAILURE if it could not find blackConnect classes - bcJavaComponentFactory.cpp check return value after calling bcJavaStubsAndProxies and fail if it fails ------------------------------------------- Ed will you please review my patch. Thanks, Igor
Looks good r=edburns
checked into the trunk closed as fixed
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Work now. Mark VERIFIED
Status: RESOLVED → VERIFIED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: