On Sep 16, 2009, at 11:29 AM, Steve Cronin wrote:

Jonathan;

Yeah thanks for asking that -  I should have made it clearer.

NO crash report - just program death (hang no response)

The earlier emails include extracts from my own logs that I have the users turn on.

So the program is spinning with a beach ball? If so, have you tried asking a user to sample the problem with "sample MyProgramName" from the terminal? That will tell you what your program is doing as it hangs.

Jon Hess


Steve

On Sep 16, 2009, at 1:22 PM, Jonathan Hess wrote:


On Sep 16, 2009, at 12:46 AM, Steve Cronin wrote:

Folks;

Got another report today from the field also a MacBookPro5,1 running 10.5.8 2009-09-16 03:01:53.954 XYZ[329:20b] Error loading /Library/ ScriptingAdditions/QXPScriptingAdditions.osax/Contents/MacOS/ QXPScriptingAdditions: dlopen(/Library/ScriptingAdditions/ QXPScriptingAdditions.osax/Contents/MacOS/QXPScriptingAdditions, 262): no suitable image found. Did find: /Library/ScriptingAdditions/QXPScriptingAdditions.osax/Contents/ MacOS/QXPScriptingAdditions: mach-o, but wrong architecture 2009-09-16 03:01:54.150 XYZ[329:20b] HIToolbox: ignoring exception '*** -[NSCFString substringToIndex:]: Range or index out of bounds' that raised inside Carbon event dispatch

My released app dies immediately afterwards..
What the heck is going on here?
I've compiled the app with XC & IB 3.2 w/ a 10.4 deployment
10.6 SDK (32-bit universal --  i36 ppc ppc7400 ppc970 x86_64)

How I do I hone in on where the problem is??

Do you have a crash report? If so, does it have a backtrace of where the exception occurred?

Jon Hess

Steve

On Sep 15, 2009, at 1:50 AM, Graham Cox wrote:


On 15/09/2009, at 4:44 PM, Steve Cronin wrote:

15:01:38.292 XYZ[11756:20b] HIToolbox: ignoring exception '***
-[NSCFString substringToIndex:]: Range or index out of bounds' that raised
inside Carbon event dispatch

This is occurring just as nib is about to open a first window.
I've not seen this before and do not see it on my development machines (debug or release)
Reporting machine is MacBookPro5,1 - 10.5.8


Is the report coming from a Snow Leopard machine? I've seen a few of these running on Snow Leopard. My guess is that previously the exception was silently ignored, now it's logging. The exception will still be occurring on 10.4/10.5, just not being noticed. So there is a bug there that you should probably fix.

--Graham



_______________________________________________

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/jhess%40apple.com

This email sent to jh...@apple.com



_______________________________________________

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Reply via email to