# Debugger fails on pycall

**URL:** https://discourse.julialang.org/t/debugger-fails-on-pycall/23560
**Category:** General Usage
**Tags:** debug
**Created:** [April 26, 2019, 2:14pm UTC](https://discourse.julialang.org/t/debugger-fails-on-pycall/23560 "2019-04-26T14:14:01Z")
**Posts on this page:** 1
**Showing post:** 6

<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: [April 28, 2019, 8:46am UTC](https://discourse.julialang.org/t/debugger-fails-on-pycall/23560/6 "2019-04-28T08:46:07Z")

</div>

It is possible to write methods that are not safe to interpret (and Base has a few of them). These are special cased to run compiled by putting them in `JuliaInterpeter.compiled_methods` or `JuliaInterpreter.compiled_modules` (for compiling all functions in a module).

You can try pushing the method causing the error into `JuliaInterpeter.compiled_methods` or whole of PyCall into `JuliaInterpreter.compiled_modules` if you don’t want to debug anything going through PyCall.

---

_[View the full topic](https://discourse.julialang.org/t/debugger-fails-on-pycall/23560)._