Fabio Zadrozny

It's probably trickier than that... the issue is that the option `python -` is not properly supported to automatically attach to subprocesses (python itself would read the stdin contents to...

This is odd and shouldn't be happening (ThreadTracer uses `frame.f_code.co_filename` and that should be bytes in Python 2, not unicode -- there's only one place in `_pydevd_bundle.pydevd_trace_dispatch_regular.ThreadTracer.__call__` which calls `get_abs_path_real_path_and_base_from_frame`...

@Wilhelmsson177 which tool are you debugging? Can you pass me the stack trace when you remove the `.pyd`? (it should be a little different). Can you check if running the...

Humm, if you create an interactive console on PyDev (http://www.pydev.org/manual_adv_interactive_console.html) and attach it to a debug session (see Full `Debug Support in Interactive Console` in that page), you should be...

No, that's not a python limitation, it's only a limitation of the implementation of the pydev.debugger (it's not impossible to add that feature, it just needs work to be properly...

Unfortunately this is expected. Python itself doesn't have an API to do that... not that it's impossible to do it (through some hackery using the C-api I believe it'd be...

This is a duplicate of https://github.com/fabioz/PyDev.Debugger/issues/76

Reopening since it happens on 5.5.0. Do you have a sample test case to check it?

Unfortunately no... my guess is that for some reason the tracing calls (from sys.settrace) are not being called... The usual culprits are: - a stack overflow error is being triggered...

Which Jython version are you using?