:Gavin Sharp [email: gavin@gavinsharp.com] Reporter
	Description • 14 years ago

I'm seeing this with some changes I'm making in bug 398776. I tried narrowing down my specific example to a simple testcase, but couldn't reproduce it exactly. I did manage to find an example of a misreported exception, though, so hopefully that's enough to go on.

STR:
1) Apply this patch to services.jsm
2) run firefox -jsconsole

Expected: "uncaught exception: 1 in Services.jsm" or somesuch, followed by various "gPrefService/Services.prefs is undefined" exceptions

Actual: only the "gPrefService/Services.prefs is undefined" exceptions

	:Gavin Sharp [email: gavin@gavinsharp.com] Reporter
	Comment 1 • 14 years ago

The specific case I was looking at in bug 398776 involved a lazy getter that imports my module, and returns a new object from it. It then calls a method on it - the method throws, and the exception isn't reported. I couldn't come up with a simple testcase that shows that problem, though. 

I also tried just throwing at the top level in Services.jsm, and that exception is reported just fine.