# Bus error when doing Pkg.update() on FreeBSD 11

**URL:** <https://discourse.julialang.org/t/bus-error-when-doing-pkg-update-on-freebsd-11/5471>\
**Category:** General Usage\
**Created:** [August 20, 2017, 2:58pm UTC](https://discourse.julialang.org/t/bus-error-when-doing-pkg-update-on-freebsd-11/5471 "2017-08-20T14:58:26Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![ko56](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/ko56/32/2684_2.png) [@ko56](https://discourse.julialang.org/u/ko56)\
**Post date:** [August 20, 2017, 2:58pm UTC](https://discourse.julialang.org/t/bus-error-when-doing-pkg-update-on-freebsd-11/5471/1 "2017-08-20T14:58:26Z")

</div>

I have Julia 0.6.0 on FreeBSD 11. It is exhibiting the following behavior:

```julia
type [ko@wiley ~]$ julia
               _
   _ _ _(_)_ | A fresh approach to technical computing
  (_) | (_) (_) | Documentation: https://docs.julialang.org
   _ _ _| |_ __ _ | Type "?help" for help.
  | | | | | | |/ _` | |
  | | |_| | | | (_| | | Version 0.6.0 (2017-06-19 13:05 UTC)
 _/ |\ __'_|_|_|\__'_| |  
|__/ | amd64-unknown-freebsd11.1

julia> Pkg.update()
INFO: Updating METADATA...
INFO: Computing changes...
INFO: Upgrading DocStringExtensions: v0.3.4 => v0.4.0
INFO: Upgrading Plots: v0.12.2 => v0.12.3

signal (10): Bus error
while loading no file, in expression starting on line 0
Bus error
[ko@wiley ~]$ 

```

I’ve tried running gdb on a core dump, and the backtrace is more than 3000 lines. The most informative part seems to be the tail:

```julia
[ko@wiley ~]$ tail btr
#3113 <signal handler called>
#3114 x86_64_freebsd_fallback_frame_state (context=0x7fffdf1f6e20, context=0x7fffdf1f6e20, fs=0x7fffdf1f6b70) at ./md-unwind-support.h:60
#3115 uw_frame_state_for (context=context@entry=0x7fffdf1f6e20, fs=fs@entry=0x7fffdf1f6b70) at /wrkdirs/usr/ports/lang/gcc5/work/gcc-5.4.0/libgcc/unwind-dw2.c:1249
#3116 0x0000000805c40fdb in _Unwind_ForcedUnwind_Phase2 (exc=exc@entry=0x823aa1230, context=context@entry=0x7fffdf1f6e20) at /wrkdirs/usr/ports/lang/gcc5/work/gcc-5.4.0/libgcc/unwind.inc:155
#3117 0x0000000805c41314 in _Unwind_ForcedUnwind (exc=0x823aa1230, stop=0x805e5d7b0, stop_argument=<optimized out>) at /wrkdirs/usr/ports/lang/gcc5/work/gcc-5.4.0/libgcc/unwind.inc:207
#3118 0x0000000805e5d613 in ?? () from /lib/libthr.so.3
#3119 0x0000000805e5d42b in pthread_exit () from /lib/libthr.so.3
#3120 0x0000000805e4fbcd in ?? () from /lib/libthr.so.3
#3121 0x00007fffdeff7000 in ?? ()
Backtrace stopped: Cannot access memory at address 0x7fffdf1f7000
[ko@wiley ~]$ 

```

I don’t know what this implies. Is there some way to debug “more at the source level”? With stacktrace()?

I’ve also built julia 0.7-dev from the git repository, so that no FreeBSD system libraries are used. The problem persists.

---

<div class="post-metadata">

**Author:** ![lobingera](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/lobingera/32/211_2.png) [@lobingera](https://discourse.julialang.org/u/lobingera)\
**Post date:** [August 20, 2017, 3:13pm UTC](https://discourse.julialang.org/t/bus-error-when-doing-pkg-update-on-freebsd-11/5471/2 "2017-08-20T15:13:48Z")

</div>

i cannot judge if related, but recently:  
[https://github.com/JuliaLang/julia/issues/23328](https://github.com/JuliaLang/julia/issues/23328)

---

<div class="post-metadata">

**Author:** ![ko56](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/ko56/32/2684_2.png) [@ko56](https://discourse.julialang.org/u/ko56)\
**Post date:** [August 21, 2017, 12:49pm UTC](https://discourse.julialang.org/t/bus-error-when-doing-pkg-update-on-freebsd-11/5471/3 "2017-08-21T12:49:46Z")

</div>

Yes, this seems like the same thing.

---

<div class="post-metadata">

**Author:** ![ko56](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/ko56/32/2684_2.png) [@ko56](https://discourse.julialang.org/u/ko56)\
**Post date:** [August 22, 2017, 3:11pm UTC](https://discourse.julialang.org/t/bus-error-when-doing-pkg-update-on-freebsd-11/5471/4 "2017-08-22T15:11:43Z")

</div>

Problem solved by the fix reported for issue “Segfault in Pkg tests on FreeBSD 11.1 #23328”