Re: Crash when testing new NSSound

[Fred Kiefer]

Stefan Bidigaray wrote:
> OK, so I just finished writing the NSSound code and started testing it. 
> Well, I'm getting to really weird behaviors (one with the fall back and
> one with the libsndfile code).
> 
> When using libsndfile, I get a segmentation fault... I stepped through
> the code and get this:
> -[NSApplication sendEvent:] (self=0x26cab30, _cmd=0x7fa12efa9ae0,
>     theEvent=0x26fec70) at NSApplication.m:1968
> 1968    }
> (gdb)
> -[NSApplication run] (self=0x26cab30, _cmd=0x7fa12ef99540)
>     at NSApplication.m:1468
> 1468                  if (type != NSPeriodic && type != NSMouseMoved)
> (gdb)
> 1470                      [_listener updateServicesMenu];
> (gdb)
> 1471                      [_main_menu update];
> (gdb)
> 1474              NS_HANDLER
> (gdb)
> 1481          DESTROY (_runLoopPool);
> (gdb)
> 
> Program received signal SIGSEGV, Segmentation fault.
> 0x00007fa12de01817 in get_imp () from /usr/lib/libobjc.so.2
> 
> Let me know if you need me to go further back.  Don't really understand
> what's happening here.
> 
> When using the fall back something freezes and my test application's
> open button never pops back up.  Running GDB on that, I can see the
> problem is whenever I call [isa +_soundIsAU:] in NSSound+AU.m.  GDB
> simply stops responding.  I can still click other buttons and quit
> normally, but it just get hung up on that line.
> 
> I've attached a copy of my the diff and the sample application (and the
> .wav file I'm using, that's right bugs bunny).
> 

This may no longe rbe relevant, as you are planing to reimplement your
NSSound code. Still, when you get a segmentation fault, first do a back
trace (command bt) in gdb. This should help to get the information we
will need to track down the problem.

Fred