[chuck-users] Debugging Segmentation fault: 11

Mark Cerqueira mark.cerqueira at gmail.com
Tue Jan 27 15:36:26 EST 2015

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!


On Tue, Jan 27, 2015 at 12:31 PM, Gonzalo <gonzalo at 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 at lists.cs.princeton.edu
> https://lists.cs.princeton.edu/mailman/listinfo/chuck-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cs.princeton.edu/pipermail/chuck-users/attachments/20150127/2f78c7bb/attachment.html>

More information about the chuck-users mailing list