---
title: "Discussion on \"Debugging a segfault in a python ctypes project\" | Hashnode"
description: "Discussion on \"Debugging a segfault in a python ctypes project\". When a pure Python program crashes, a verbose traceback is printed. The traceback makes it easy to find where in your code things went wrong. However, if your Python program is wrapping some C code, you need to run through a few hoops to see what wen..."
url: "https://hashnode.com/posts/debugging-a-segfault-in-a-python-ctypes-project/63fbf72be445ddbba19550c8"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Debugging a segfault in a python ctypes project](https://astro.hashnode.dev/debugging-a-segfault-in-a-python-ctypes-project?utm_source=hashnode&utm_medium=feed)

When a pure Python program crashes, a verbose traceback is printed. The traceback makes it easy to find where in your code things went wrong. However, if your Python program is wrapping some C code, you need to run through a few hoops to see what wen...

Feb 27, 2023 · 1 min read · astro.hashnode.dev  
Read the article

-   [#python](https://hashnode.com/tag/python)
-   [#gdb](https://hashnode.com/tag/gdb)
-   [#segfault](https://hashnode.com/tag/segfault)
-   [#debugging](https://hashnode.com/tag/debugging)
-   [#ctype](https://hashnode.com/tag/ctype)

## Written by

[Danny Price](https://hashnode.com/@drdcp)

@drdcp

  
[View profile](https://hashnode.com/@drdcp)

Australian Project Scientist, Breakthrough Listen

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
