# Profile.print() lines too long

**URL:** <https://discourse.julialang.org/t/profile-print-lines-too-long/5526>\
**Category:** General Usage\
**Tags:** question\
**Created:** [August 23, 2017, 1:41pm UTC](https://discourse.julialang.org/t/profile-print-lines-too-long/5526 "2017-08-23T13:41:46Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Tamas\_Papp](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tamas_papp/32/25949_2.png) [@Tamas\_Papp](https://discourse.julialang.org/u/Tamas_Papp)\
**Post date:** [August 23, 2017, 1:41pm UTC](https://discourse.julialang.org/t/profile-print-lines-too-long/5526/1 "2017-08-23T13:41:46Z")

</div>

I am profiling some code, using the [statistical profiler](https://docs.julialang.org/en/latest/manual/profile/#Profiling-1) from `Base`, augmented with [ProfileView.jl](https://github.com/timholy/ProfileView.jl). The latter shows some functions at around depth 4-5 in the call stack that are not type stable (red).

I thought I would investigate by calling `@code_warntype`, but my problem is that `Profile.print()` lines are too long, eg:

```julia
/home/tamas/research/structural-labor-II/DurationModels.jl:77; OLS_estimate(::Array{ForwardDiff.Dual{ForwardDiff.Tag{DurationModels.DurationModel{Float64,Di...

```

where the `...` is part of the truncated output. How can I figure out the type of the call to replicate the problem? Any general advice on this is also appreciated.

---

<div class="post-metadata">

**Author:** ![kristoffer.carlsson](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/kristoffer.carlsson/32/22_2.png) [@kristoffer.carlsson](https://discourse.julialang.org/u/kristoffer.carlsson)\
**Post date:** [August 23, 2017, 1:44pm UTC](https://discourse.julialang.org/t/profile-print-lines-too-long/5526/2 "2017-08-23T13:44:39Z")

</div>

[https://docs.julialang.org/en/latest/manual/profile/#Options-for-controlling-the-display-of-profile-results-1](https://docs.julialang.org/en/latest/manual/profile/#Options-for-controlling-the-display-of-profile-results-1)

"  
File/function names are sometimes truncated (with …), and indentation is truncated with a +n at the beginning, where n is the number of extra spaces that would have been inserted, had there been room. If you want a complete profile of deeply-nested code, often a good idea is to save to a file using a wide `displaysize` in an `IOContext`:

```julia
open("/tmp/prof.txt", "w") do s
    Profile.print(IOContext(s, :displaysize => (24, 500)))
end

```

"