报告和分析崩溃（段错误）

    If you’ve been directed to this page, find the symptom that best matches what you’re experiencing and follow the instructions to generate the debugging information requested. Table of symptoms:

    No matter the error, we will always need to know what version of Julia you are running. When Julia first starts up, a header is printed out with a version number and date. Please also include the output of (exported from the InteractiveUtils standard library) in any report you create:

    Segfaults during bootstrap (sysimg.jl))

    Segfaults toward the end of the make process of building Julia are a common symptom of something going wrong while Julia is preparsing the corpus of code in the base/ folder. Many factors can contribute toward this process dying unexpectedly, however it is as often as not due to an error in the C-code portion of Julia, and as such must typically be debugged with a debug build inside of gdb. Explicitly:

    Create a debug build of Julia:

    1. $ cd <julia_root>
    2. $ make debug

    Note that this process will likely fail with the same error as a normal make incantation, however this will create a debug executable that will offer gdb the debugging symbols needed to get accurate backtraces. Next, manually run the bootstrap process inside of gdb:

    1. $ cd base/
    2. $ gdb -x ../contrib/debug_bootstrap.gdb

    The procedure is very similar to ). Create a debug build of Julia, and run your script inside of a debugged Julia process:

    Note that will sit there, waiting for instructions. Type r to run the process, and bt to generate a backtrace once it segfaults:

    1. (gdb) r
    2. ...
    3. (gdb) bt

    Create a gist with the backtrace, the , and any other pertinent information you can think of and open a new issue on Github with a link to the gist.

    Errors during Julia startup

    Occasionally errors occur during Julia’s startup process (especially when using binary distributions, as opposed to compiling from source) such as the following:

    1. $ julia
    2. exec: error -5

    These errors typically indicate something is not getting loaded properly very early on in the bootup phase, and our best bet in determining what’s going wrong is to use external tools to audit the disk activity of the julia process:

    • On OSX, use dtruss:

      1. $ dtruss -f julia

    Create a with the / dtruss output, the version info, and any other pertinent information and open a new on Github with a link to the gist.

    As mentioned elsewhere, julia has good integration with rr for generating traces; this includes, on Linux, the ability to automatically run julia under rr and share the trace after a crash. This can be immensely helpful when debugging such crashes and is strongly encouraged when reporting crash issues to the JuliaLang/julia repo. To run julia under rr automatically, do:

      To generate the rr trace locally, but not share, you can do:

      Note that this is only works on Linux. The blog post on Time Travelling Bug Reporting has many more details.

      Glossary

      • <julia_root> refers to the root directory of the Julia source tree; e.g. it should contain folders such as base, deps, , test, etc…..