Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Segmentation fault #21

Open
rgrinberg opened this issue May 24, 2018 · 2 comments
Open

Segmentation fault #21

rgrinberg opened this issue May 24, 2018 · 2 comments

Comments

@rgrinberg
Copy link
Contributor

This is on 4.06.0. Here's the backtrace:

(lldb) bt
* thread #1, stop reason = signal SIGSTOP
  * frame #0: 0x0000000105dad0c8 prof_spacetime.exe`camlProf_spacetime_lib__Series__create_1052 + 8
    frame #1: 0x0000000105daa9a7 prof_spacetime.exe`camlProf_spacetime__main_1284 + 295
    frame #2: 0x0000000105dc3c98 prof_spacetime.exe`camlCmdliner_term__fun_1416 + 104
    frame #3: 0x0000000105dc6c3a prof_spacetime.exe`camlCmdliner__run_1502 + 170
    frame #4: 0x0000000105dc6edc prof_spacetime.exe`camlCmdliner__term_eval_1550 + 300
    frame #5: 0x0000000105dc7b95 prof_spacetime.exe`camlCmdliner__eval_choice_inner_2477 + 325
    frame #6: 0x0000000105dabc99 prof_spacetime.exe`camlProf_spacetime__entry + 3721
    frame #7: 0x0000000105da7619 prof_spacetime.exe`caml_program + 3817
    frame #8: 0x0000000105ff3470 prof_spacetime.exe`caml_start_program + 92
    frame #9: 0x0000000105fd46fc prof_spacetime.exe`caml_startup_common(argv=0x00007ffee9e58b98, pooling=<unavailable>) at startup.c:156 [opt]
    frame #10: 0x0000000105fd476b prof_spacetime.exe`caml_main [inlined] caml_startup_exn(argv=<unavailable>) at startup.c:161 [opt]
    frame #11: 0x0000000105fd4764 prof_spacetime.exe`caml_main [inlined] caml_startup(argv=<unavailable>) at startup.c:166 [opt]
    frame #12: 0x0000000105fd4764 prof_spacetime.exe`caml_main(argv=<unavailable>) at startup.c:173 [opt]
    frame #13: 0x0000000105fd47dc prof_spacetime.exe`main(argc=<unavailable>, argv=<unavailable>) at main.c:44 [opt]
    frame #14: 0x00007fff54221015 libdyld.dylib`start + 1
    frame #15: 0x00007fff54221015 libdyld.dylib`start + 1
@lpw25
Copy link
Owner

lpw25 commented Jun 6, 2018

What was the command? It's probably some marshalling issue. I don't think we use any magic numbers yet to stop us from trying to unmarshal the wrong files.

@rgrinberg
Copy link
Contributor Author

rgrinberg commented Jun 7, 2018 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants