As you probably suspected, the Terminal launch still works, even with
nonsense environment values (why should NetBeans care about the
values since
it probably doesn't even use the variables?).
I also tried setting JAVA_HOME to the same nonsense value and the
Terminal
launch still works.
Hmm, that isn't what I expected. I thought there was a good chance
it would crash.
I'm not sure what this tells us about the problem, though. Maybe
just that the crash is related to only the parsing of args and env-
vars, not their actual usage.
Unfortunately, the Finder launch did not work (same crash). Looking
at the
debugging file generated by the launch attempt verifies that the
environment
variables were, I fact, created.
That's surprising. I'm not sure what that tells us about the
problem, either, but it does close off one possible work-around. Oh
well.
Next, I tried the LSExecutableArchitectures key (just for fun) as
follows:
I would expect this to have no effect.
The executable in NB.app is a shell script, so it doesn't have
different architectures, so there's nothing that
LSExecutableArchitectures applies to.
I went back to the original .plist and put the -arch workaround
back into
nbexec as a sanity check.
Finder launch worked again.
Interesting results (in a negative sort of wary).
Agreed. Please be sure to mention them in your bug report, though.
It could be a clue to solving the problem, or just a way to avoid
trying some non-functional work-around.
-----
I noticed that the Info.plist you posted lacks a CFBundleIdentifier
key. This can sometimes cause weird things to happen. I'd be
surprised if it's related to the crash, but I've been surprised before.
-- GG
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Java-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/java-dev/email@hidden
