python tracing a segmentation fault

by

If you are on linux, run python under gdb

gdb python
(gdb) run /path/to/script.py
## wait for segfault ##
(gdb) backtrace
## stack trace of the c code

More Related Contents:

  1. How to debug a Flask app
  2. How can I see the entire HTTP request that’s being sent by my Python application?
  3. Showing the stack trace from a running Python application
  4. How to debug in Django, the good way? [closed]
  5. What is the internal precision of numpy.float128?
  6. Why (0-6) is -6 = False? [duplicate]
  7. How do I run a Python program?
  8. Is it feasible to compile Python to machine code?
  9. Speed comparison with Project Euler: C vs Python vs Erlang vs Haskell
  10. Wrapping a C library in Python: C, Cython or ctypes?
  11. It is more efficient to use if-return-return or if-else-return?
  12. What are good ways to make my Python code run first time? [closed]
  13. Accessing OpenCV CUDA Functions from Python (No PyCUDA)
  14. I have Python on my Ubuntu system, but gcc can’t find Python.h
  15. Create an object using Python’s C API
  16. How to compile .c code from Cython with gcc
  17. Where can I find source or algorithm of Python’s hash() function?
  18. Python ? (conditional/ternary) operator for assignments [duplicate]
  19. Using Cython To Link Python To A Shared Library
  20. Pretty print a pandas dataframe in VS Code
  21. C++ conversion from NumPy array to Mat (OpenCV)
  22. How can I tell where my python script is hanging?
  23. pydev breakpoints not working
  24. Embedding Python in C, linking fails with undefined reference to `Py_Initialize’
  25. How to watch for a variable change in python without dunder setattr or pdb
  26. Writing code translator from Python to C? [closed]
  27. Installing lxml for Python 3.4 on Windows x 86 (32 bit) with Visual Studio C++ 2010 Express
  28. Extract traceback info from an exception object
  29. Extending python – to swig, not to swig or Cython
  30. Call python code from c via cython

Leave a Comment