In general, a useful strategy is to make a debug build then attach a debugger. A simple usage pattern:
make debug #builds julia-debug gdb julia-debug #or lldb julia-debug #gdb will load r #short for run program #do stuff in julia to cause segfault bt #print backtrace Once you have trapped the segfault you can also do fancier things like print variables in individual stack frames. But you can get quite far just by obtaining the backtrace. Thanks, Jiahao Chen Staff Research Scientist MIT Computer Science and Artificial Intelligence Laboratory On Mon, Jan 19, 2015 at 1:09 AM, Ivar Nesje <iva...@gmail.com> wrote: > Pretty much anything. Compiler bugs are certainly possible, but also bugs > in the standard library. Generally pure Julia code shouldn't segfault, > unless you're using ccall or the unsafe_ family. > > If you can post a link to a reasonably short segfaulting example here, > there is a good chance that someone will look at it and find the bug.
