[racket] why a segfault on the command line, but not in DrRacket?

From: Matthew Butterick (mb at mbtype.com)
Date: Tue Dec 30 13:47:01 EST 2014

I have a program that consistently works in DrRacket regardless of input size. 

But on the command line, once input exceeds a certain threshold, the program consistently dies with a "Segmentation fault: 11 (core dumped)" error (though it works with smaller files). I'm invoking `racket` without any special flags, like so:

racket main.rkt

I know which line of my program is triggering the segfault. But since the error is related to the input size and the use of command-line Racket, I think I ought to look elsewhere for the cause.

Are there particular command-line flags that can be helpful in diagnosing segfaults? Is a segfault like this typically due to running out of memory?

Posted on the users mailing list.