Segmentation Fault on Argument Error

[schlurp]

               _
   _       _ _(_)_     |  Documentation: https://docs.julialang.org
  (_)     | (_) (_)    |
   _ _   _| |_  __ _   |  Type "?" for help, "]?" for Pkg help.
  | | | | | | |/ _` |  |
  | | |_| | | | (_| |  |  Version 1.3.0-DEV.0 (2019-04-10)
 _/ |\__'_|_|_|\__'_|  |  Commit 62d7ec55fd (0 days old master)
|__/                   |

julia> versioninfo()
Julia Version 1.3.0-DEV.0
Commit 62d7ec55fd (2019-04-10 19:08 UTC)
Platform Info:
  OS: Linux (x86_64-linux-gnu)
  CPU: Intel(R) Core(TM) i7-7820HQ CPU @ 2.90GHz
  WORD_SIZE: 64
  LIBM: libopenlibm
  LLVM: libLLVM-6.0.1 (ORCJIT, skylake)

When supplying a non-integer to the -p option, julia segfaults after printing an error message. Reproduce with

$ ./julia -p blubb
ERROR: julia: -p,--procs=<n> must be an integer >= 1
Segmentation fault

Valgrind output is

$ valgrind julia -p blubb
sh: 0: getcwd() failed: No such file or directory
==12813== Memcheck, a memory error detector
==12813== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==12813== Using Valgrind-3.14.0 and LibVEX; rerun with -h for copyright info
==12813== Command: julia -p blubb
==12813== 
ERROR: julia: -p,--procs=<n> must be an integer >= 1
==12813== Invalid read of size 8
==12813==    at 0x489E87B: jl_mutex_unlock (locks.h:166)
==12813==    by 0x489E87B: jl_atexit_hook (init.c:294)
==12813==    by 0x48BBBF6: jl_exit (jl_uv.c:613)
==12813==    by 0x48EE3C5: jl_vexceptionf (rtutils.c:53)
==12813==    by 0x48EE4F7: jl_errorf (rtutils.c:75)
==12813==    by 0x48E0C9F: jl_parse_opts (jloptions.c:400)
==12813==    by 0x10A2FE: main (repl.c:210)
==12813==  Address 0xfffffffffffffff8 is not stack'd, malloc'd or (recently) free'd
==12813== 
==12813== 
==12813== Process terminating with default action of signal 11 (SIGSEGV)
==12813==  Access not within mapped region at address 0xFFFFFFFFFFFFFFF8
==12813==    at 0x489E87B: jl_mutex_unlock (locks.h:166)
==12813==    by 0x489E87B: jl_atexit_hook (init.c:294)
==12813==    by 0x48BBBF6: jl_exit (jl_uv.c:613)
==12813==    by 0x48EE3C5: jl_vexceptionf (rtutils.c:53)
==12813==    by 0x48EE4F7: jl_errorf (rtutils.c:75)
==12813==    by 0x48E0C9F: jl_parse_opts (jloptions.c:400)
==12813==    by 0x10A2FE: main (repl.c:210)
==12813==  If you believe this happened as a result of a stack
==12813==  overflow in your program's main thread (unlikely but
==12813==  possible), you can try to increase the size of the
==12813==  main thread stack using the --main-stacksize= flag.
==12813==  The main thread stack size used in this run was 8388608.
==12813== 
==12813== HEAP SUMMARY:
==12813==     in use at exit: 504,610 bytes in 1,147 blocks
==12813==   total heap usage: 1,211 allocs, 64 frees, 660,310 bytes allocated
==12813== 
==12813== LEAK SUMMARY:
==12813==    definitely lost: 0 bytes in 0 blocks
==12813==    indirectly lost: 0 bytes in 0 blocks
==12813==      possibly lost: 0 bytes in 0 blocks
==12813==    still reachable: 504,610 bytes in 1,147 blocks
==12813==         suppressed: 0 bytes in 0 blocks
==12813== Rerun with --leak-check=full to see details of leaked memory
==12813== 
==12813== For counts of detected and suppressed errors, rerun with: -v
==12813== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)
Segmentation fault