# Segmentation fault in executable after compilation with juliac including --trim --experimental arguments

**URL:** https://discourse.julialang.org/t/segmentation-fault-in-executable-after-compilation-with-juliac-including-trim-experimental-arguments/125303
**Category:** General Usage
**Tags:** compilation, juliac
**Created:** [January 28, 2025, 2:49pm UTC](https://discourse.julialang.org/t/segmentation-fault-in-executable-after-compilation-with-juliac-including-trim-experimental-arguments/125303 "2025-01-28T14:49:18Z")
**Posts on this page:** 1
**Showing post:** 5

<div class="post-metadata">

### Author: ![asprionj](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/asprionj/32/6856_2.png) [@asprionj](https://discourse.julialang.org/u/asprionj)
#### Post date: [August 18, 2025, 9:10pm UTC](https://discourse.julialang.org/t/segmentation-fault-in-executable-after-compilation-with-juliac-including-trim-experimental-arguments/125303/5 "2025-08-18T21:10:39Z")

</div>

Does this workaround also hold for when other packages are used (`using` or `importing` them)? See my description here: [Creating fully self-contained and pre-compiled library - #14 by asprionj](https://discourse.julialang.org/t/creating-fully-self-contained-and-pre-compiled-library/131374/14).

Would these be added inside the `Module`, I assume? And also added to an environment of which the path to `Project.toml` would be specified to the `julia --project=<path> juliac.jl ...` call?

---

_[View the full topic](https://discourse.julialang.org/t/segmentation-fault-in-executable-after-compilation-with-juliac-including-trim-experimental-arguments/125303)._