Crash(?) Questions

  • I am beta testing a new release with 4 users.  One in Norway gets this when launching the program:

    Process:        Embrilliance [262]
    Path:            /Applications/Embrilliance.app/Contents/MacOS/Embrilliance
    Identifier:      com.britonleap.Embrilliance
    Version:        ??? (???)
    Code Type:      X86 (Native)
    Parent Process:  launchd [123]

    Interval Since Last Report:          2478349 sec
    Crashes Since Last Report:          67
    Per-App Interval Since Last Report:  0 sec
    Per-App Crashes Since Last Report:  16

    Date/Time:      2012-06-11 22:30:37.306 +0200
    OS Version:      Mac OS X 10.5.8 (9L30)
    Report Version:  6
    Anonymous UUID:  209D675C-1E6A-4784-85AE-B410AA1348C9

    Exception Type:  EXC_BREAKPOINT (SIGTRAP)
    Exception Codes: 0x0000000000000002, 0x0000000000000000
    Crashed Thread:  0

    Dyld Error Message:
      Symbol not found: __NSConcreteStackBlock
      Referenced from: /Applications/Embrilliance.app/Contents/MacOS/Embrilliance
      Expected in: /usr/lib/libSystem.B.dylib

    I have never seen this and am looking for some guidance.

    -koko
  • On Jun 11, 2012, at 2:14 PM, koko <koko...> wrote:
    > I am beta testing a new release with 4 users.  One in Norway gets this when launching the program:
    >
    > Process:        Embrilliance [262]
    > Path:            /Applications/Embrilliance.app/Contents/MacOS/Embrilliance
    > Identifier:      com.britonleap.Embrilliance
    > Version:        ??? (???)
    > Code Type:      X86 (Native)
    > Parent Process:  launchd [123]
    >
    > Interval Since Last Report:          2478349 sec
    > Crashes Since Last Report:          67
    > Per-App Interval Since Last Report:  0 sec
    > Per-App Crashes Since Last Report:  16
    >
    > Date/Time:      2012-06-11 22:30:37.306 +0200
    > OS Version:      Mac OS X 10.5.8 (9L30)
    > Report Version:  6
    > Anonymous UUID:  209D675C-1E6A-4784-85AE-B410AA1348C9
    >
    > Exception Type:  EXC_BREAKPOINT (SIGTRAP)
    > Exception Codes: 0x0000000000000002, 0x0000000000000000
    > Crashed Thread:  0
    >
    > Dyld Error Message:
    > Symbol not found: __NSConcreteStackBlock
    > Referenced from: /Applications/Embrilliance.app/Contents/MacOS/Embrilliance
    > Expected in: /usr/lib/libSystem.B.dylib

    Your app uses block objects. This user is trying to run it on 10.5.8. Block objects are unavailable on 10.5.8.

    It is sometimes possible to arrange your code and build settings to use block objects only on 10.6+.

    --
    Greg Parker    <gparker...>    Runtime Wrangler
  • On Jun 11, 2012, at 4:14 PM, koko wrote:

    > I am beta testing a new release with 4 users.  One in Norway gets this when launching the program:
    >
    > Process:        Embrilliance [262]
    > Path:            /Applications/Embrilliance.app/Contents/MacOS/Embrilliance
    > Identifier:      com.britonleap.Embrilliance
    > Version:        ??? (???)
    > Code Type:      X86 (Native)
    > Parent Process:  launchd [123]
    >
    > Interval Since Last Report:          2478349 sec
    > Crashes Since Last Report:          67
    > Per-App Interval Since Last Report:  0 sec
    > Per-App Crashes Since Last Report:  16
    >
    > Date/Time:      2012-06-11 22:30:37.306 +0200
    > OS Version:      Mac OS X 10.5.8 (9L30)
    > Report Version:  6
    > Anonymous UUID:  209D675C-1E6A-4784-85AE-B410AA1348C9
    >
    > Exception Type:  EXC_BREAKPOINT (SIGTRAP)
    > Exception Codes: 0x0000000000000002, 0x0000000000000000
    > Crashed Thread:  0
    >
    > Dyld Error Message:
    > Symbol not found: __NSConcreteStackBlock
    > Referenced from: /Applications/Embrilliance.app/Contents/MacOS/Embrilliance
    > Expected in: /usr/lib/libSystem.B.dylib

    This is an app that uses blocks being launched on Leopard, which doesn't have the runtime support necessary to support blocks.

    You should set your deployment target to at least 10.6 and, if Xcode doesn't do it for you, set the LSMinimumSystemVersion key in your Info.plist to "10.6.0".

    Or, if you need to support Leopard users, you need to restrict yourself to features of the runtime and frameworks which are compatible.

    Regards,
    Ken
  • I understand the Block Objects discussion.  However these would not come in to play until the  App was running and the user chose a file ope or save which uses block for the 'callback'.

    This error occurs on launch.  I did not think that the 'mach loader' checked all symbols at launch ..,

    -koko

    On Jun 11, 2012, at 3:29 PM, Greg Parker wrote:

    > On Jun 11, 2012, at 2:14 PM, koko <koko...> wrote:
    >> I am beta testing a new release with 4 users.  One in Norway gets this when launching the program:
    >>
    >> Process:        Embrilliance [262]
    >> Path:            /Applications/Embrilliance.app/Contents/MacOS/Embrilliance
    >> Identifier:      com.britonleap.Embrilliance
    >> Version:        ??? (???)
    >> Code Type:      X86 (Native)
    >> Parent Process:  launchd [123]
    >>
    >> Interval Since Last Report:          2478349 sec
    >> Crashes Since Last Report:          67
    >> Per-App Interval Since Last Report:  0 sec
    >> Per-App Crashes Since Last Report:  16
    >>
    >> Date/Time:      2012-06-11 22:30:37.306 +0200
    >> OS Version:      Mac OS X 10.5.8 (9L30)
    >> Report Version:  6
    >> Anonymous UUID:  209D675C-1E6A-4784-85AE-B410AA1348C9
    >>
    >> Exception Type:  EXC_BREAKPOINT (SIGTRAP)
    >> Exception Codes: 0x0000000000000002, 0x0000000000000000
    >> Crashed Thread:  0
    >>
    >> Dyld Error Message:
    >> Symbol not found: __NSConcreteStackBlock
    >> Referenced from: /Applications/Embrilliance.app/Contents/MacOS/Embrilliance
    >> Expected in: /usr/lib/libSystem.B.dylib
    >
    > Your app uses block objects. This user is trying to run it on 10.5.8. Block objects are unavailable on 10.5.8.
    >
    > It is sometimes possible to arrange your code and build settings to use block objects only on 10.6+.
    >
    >
    > --
    > Greg Parker    <gparker...>    Runtime Wrangler
    >
    >
  • On Jun 11, 2012, at 5:29 PM, koko wrote:

    > This error occurs on launch.  I did not think that the 'mach loader' checked all symbols at launch ..,

    Sure it does, unless they're marked as weak imports.

    —Jens
  • On Jun 11, 2012, at 5:29 PM, koko wrote:

    > I understand the Block Objects discussion.  However these would not come in to play until the  App was running and the user chose a file ope or save which uses block for the 'callback'.
    >
    > This error occurs on launch.  I did not think that the 'mach loader' checked all symbols at launch ..,

    You should probably familiarize yourself with how dynamic loaders work, then.

    --Kyle Sluder
  • On Jun 11, 2012, at 5:29 PM, koko <koko...> wrote:
    > I understand the Block Objects discussion.  However these would not come in to play until the  App was running and the user chose a file ope or save which uses block for the 'callback'.
    >
    > This error occurs on launch.  I did not think that the 'mach loader' checked all symbols at launch ...

    Symbols references are enforced at launch time, except for the ones marked as weak import.

    What version of Xcode are you using? What compiler and SDK are you using? What is your project's Deployment Target setting?

    The symbols for block objects should have been marked as weak import if you are using a sufficiently new OS X SDK and your Deployment Target is set correctly. Then your app would have been able to launch and run as long as it did not actually use block objects on 10.5.8.

    --
    Greg Parker    <gparker...>    Runtime Wrangler
  • http://mikeabdullah.net/leopard+blocks.html

    On 11 Jun 2012, at 14:14, koko wrote:

    > I am beta testing a new release with 4 users.  One in Norway gets this when launching the program:
    >
    > Process:        Embrilliance [262]
    > Path:            /Applications/Embrilliance.app/Contents/MacOS/Embrilliance
    > Identifier:      com.britonleap.Embrilliance
    > Version:        ??? (???)
    > Code Type:      X86 (Native)
    > Parent Process:  launchd [123]
    >
    > Interval Since Last Report:          2478349 sec
    > Crashes Since Last Report:          67
    > Per-App Interval Since Last Report:  0 sec
    > Per-App Crashes Since Last Report:  16
    >
    > Date/Time:      2012-06-11 22:30:37.306 +0200
    > OS Version:      Mac OS X 10.5.8 (9L30)
    > Report Version:  6
    > Anonymous UUID:  209D675C-1E6A-4784-85AE-B410AA1348C9
    >
    > Exception Type:  EXC_BREAKPOINT (SIGTRAP)
    > Exception Codes: 0x0000000000000002, 0x0000000000000000
    > Crashed Thread:  0
    >
    > Dyld Error Message:
    > Symbol not found: __NSConcreteStackBlock
    > Referenced from: /Applications/Embrilliance.app/Contents/MacOS/Embrilliance
    > Expected in: /usr/lib/libSystem.B.dylib
    >
    >
    > I have never seen this and am looking for some guidance.
    >
    > -koko
  • Yes, I was using  beginSheetModalForWindow: completionHandler

    So I have changed to:

    [NSApp beginSheet:op modalForWindow:[self window] modalDelegate:self didEndSelector:@selector(sheetDidEnd:returnCode:contextInfo:) contextInfo:nil];

    - (void)sheetDidEnd:(NSWindow *)sheet returnCode:(NSInteger)returnCode contextInfo:(void *)contextInfo
    {

    }

    Now, the didEndSelector is not being called … this makes no sense

    Suggestions please …

    -koko

    On Jun 11, 2012, at 10:21 PM, Mike Abdullah wrote:

    > http://mikeabdullah.net/leopard+blocks.html
    >
    > On 11 Jun 2012, at 14:14, koko wrote:
    >
    >> I am beta testing a new release with 4 users.  One in Norway gets this when launching the program:
    >>
    >> Process:        Embrilliance [262]
    >> Path:            /Applications/Embrilliance.app/Contents/MacOS/Embrilliance
    >> Identifier:      com.britonleap.Embrilliance
    >> Version:        ??? (???)
    >> Code Type:      X86 (Native)
    >> Parent Process:  launchd [123]
    >>
    >> Interval Since Last Report:          2478349 sec
    >> Crashes Since Last Report:          67
    >> Per-App Interval Since Last Report:  0 sec
    >> Per-App Crashes Since Last Report:  16
    >>
    >> Date/Time:      2012-06-11 22:30:37.306 +0200
    >> OS Version:      Mac OS X 10.5.8 (9L30)
    >> Report Version:  6
    >> Anonymous UUID:  209D675C-1E6A-4784-85AE-B410AA1348C9
    >>
    >> Exception Type:  EXC_BREAKPOINT (SIGTRAP)
    >> Exception Codes: 0x0000000000000002, 0x0000000000000000
    >> Crashed Thread:  0
    >>
    >> Dyld Error Message:
    >> Symbol not found: __NSConcreteStackBlock
    >> Referenced from: /Applications/Embrilliance.app/Contents/MacOS/Embrilliance
    >> Expected in: /usr/lib/libSystem.B.dylib
    >>
    >>
    >> I have never seen this and am looking for some guidance.
    >>
    >> -koko
    >
    >
  • On 12 Jun 2012, at 11:00, koko wrote:

    > Yes, I was using  beginSheetModalForWindow: completionHandler
    >
    > So I have changed to:
    >
    > [NSApp beginSheet:op modalForWindow:[self window] modalDelegate:self didEndSelector:@selector(sheetDidEnd:returnCode:contextInfo:) contextInfo:nil];
    >
    > - (void)sheetDidEnd:(NSWindow *)sheet returnCode:(NSInteger)returnCode contextInfo:(void *)contextInfo
    > {
    >
    > }
    >
    > Now, the didEndSelector is not being called … this makes no sense
    >
    > Suggestions please …

    What kind of window is this?
  • op is an NSOpenPanel

    [self window] is an NSWindow owned by a NSWindowController subclass

    -koko

    On Jun 12, 2012, at 12:20 PM, Mike Abdullah wrote:

    >
    > On 12 Jun 2012, at 11:00, koko wrote:
    >
    >> Yes, I was using  beginSheetModalForWindow: completionHandler
    >>
    >> So I have changed to:
    >>
    >> [NSApp beginSheet:op modalForWindow:[self window] modalDelegate:self didEndSelector:@selector(sheetDidEnd:returnCode:contextInfo:) contextInfo:nil];
    >>
    >> - (void)sheetDidEnd:(NSWindow *)sheet returnCode:(NSInteger)returnCode contextInfo:(void *)contextInfo
    >> {
    >>
    >> }
    >>
    >> Now, the didEndSelector is not being called … this makes no sense
    >>
    >> Suggestions please …
    >
    > What kind of window is this?
    >
  • On 13/06/2012, at 4:34 AM, koko wrote:

    > op is an NSOpenPanel

    that class has its own -beginSheetModal... method - you should use that.

    --Graham
previous month june 2012 next month
MTWTFSS
        1 2 3
4 5 6 7 8 9 10
11 12 13 14 15 16 17
18 19 20 21 22 23 24
25 26 27 28 29 30  
Go to today