Yeah, that's what I'm trying but it's hard because it only happens very sporadically, so I can never be sure that things are ok when I disable some components.

On 28/01/2015 7:36 am, Mark Cerqueira wrote:

Try binary debugging with comments! Start commenting out chunks of code
and see if you can get it to stop happening. Then start cutting back on
commented out components. Maybe start with all your audio code?

Good luck!

mc

On Tue, Jan 27, 2015 at 12:31 PM, Gonzalo <gonzalo@dense13.com
<mailto:gonzalo@dense13.com>> wrote:

    Hi,

    On a project I'm working on, I sometimes get a "Segmentation fault:
    11" error, and the program crashes. But I can't figure out when it
    happens, and cannot reproduce it. It's a big project, with many
    components communicating via events, and I have no idea who's
    triggering the problem. My question is how would you go about
    debugging this? Any ideas what can be triggering it? It sounds very
    generic...

    Probably unrelated, but just in case, I also got this (only once so
    far):

    chuck(22226,0x7fff790ee310) malloc: *** error for object
    0x1028f3408: incorrect checksum for freed object - object was
    probably modified after being freed.
    *** set a breakpoint in malloc_error_break to debug
    Abort trap: 6

    Thanks!
    Gonzalo
    _________________________________________________
    chuck-users mailing list
    chuck-users@lists.cs.__princeton.edu
    <mailto:chuck-users@lists.cs.princeton.edu>
    https://lists.cs.princeton.__edu/mailman/listinfo/chuck-__users
    <https://lists.cs.princeton.edu/mailman/listinfo/chuck-users>




_______________________________________________
chuck-users mailing list
chuck-users@lists.cs.princeton.edu
https://lists.cs.princeton.edu/mailman/listinfo/chuck-users

_______________________________________________
chuck-users mailing list
chuck-users@lists.cs.princeton.edu
https://lists.cs.princeton.edu/mailman/listinfo/chuck-users