Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 327512

Summary:	SWT fails to load if DefaultApp.nib is not available
Product:	[Eclipse Project] Platform	Reporter:	Prakash Rangaraj <prakash>
Component:	SWT	Assignee:	Platform-SWT-Inbox <platform-swt-inbox>
Status:	RESOLVED WORKSFORME	QA Contact:
Severity:	normal
Priority:	P3	CC:	lshanmug, skovatch
Version:	3.7	Keywords:	triaged
Target Milestone:	---
Hardware:	PC
OS:	Mac OS X
Whiteboard:	stalebug

Description Prakash Rangaraj

2010-10-12 02:48:25 EDT

SWT tries to load the DefaultApp.nib from the JavaVMFramework. When the file is not available, it tries to create the main menu and fails.

As per Scott, the code just a safe guard against Apple moving those files, and not normally run.

Comment 1 Scott Kovatch

2010-10-12 13:03:41 EDT

Can you attach a crash log? I'm not seeing this on 10.6 with HEAD.

Comment 2 Prakash Rangaraj

2010-10-12 13:18:52 EDT

There is no stack trace. It fails at Display:916 (where the title is initialized)  and prints "Invalid memory access of location 0x8 rip=0x7fff823d0377" on the console


Am on 10.5, probably that might make the difference

Comment 3 Scott Kovatch

2010-10-12 13:45:06 EDT

(In reply to comment #2)
> There is no stack trace. It fails at Display:916 (where the title is
> initialized)  and prints "Invalid memory access of location 0x8
> rip=0x7fff823d0377" on the console

I meant a native crash log. Open up Console.app and look for a crash log in ~/Library/Logs/CrashReporter.

But, when I see that location, that makes me think you passed null to something that couldn't handle it.  Did SWT.getMessage() fail? getApplicationName() will return SWT if none of the other cases hold.

> Am on 10.5, probably that might make the difference

Possibly. I am on 10.6, but that's a pretty straightforward line of code.

Comment 4 Lakshmi P Shanmugam

2017-07-03 08:40:06 EDT

Bug triaged, visit https://wiki.eclipse.org/SWT/Devel/Triage for more
information.

Comment 5 Eclipse Genie

2019-12-22 18:53:45 EST

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.

Comment 6 Lakshmi P Shanmugam

2019-12-23 06:08:58 EST

Closing, no response in a long time.