---
title: "Discussion on \"Reading a crash log when you have no symbols\" | Hashnode"
description: "Discussion on \"Reading a crash log when you have no symbols\". Reading a crash log when you have no symbols\nA crash log gives you the place where the machine stopped. It rarely gives you the place where the bug started. A bad pointer can travel through ten functi"
url: "https://hashnode.com/posts/reading-a-crash-log-when-you-have-no-symbols/6af4435e23d2de42a1ccc5fa"
---

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

Discussion

# [Reading a crash log when you have no symbols](https://parsaaftabi.hashnode.dev/reading-a-crash-log-when-you-have-no-symbols?utm_source=hashnode&utm_medium=feed)

Reading a crash log when you have no symbols A crash log gives you the place where the machine stopped. It rarely gives you the place where the bug started. A bad pointer can travel through ten functi

21h ago · 4 min read · parsaaftabi.hashnode.dev  
Read the article

-   [#kernel](https://hashnode.com/tag/kernel)
-   [#debugging](https://hashnode.com/tag/debugging)
-   [#osdev](https://hashnode.com/tag/osdev)

## Written by

[Parsa Aftabi](https://hashnode.com/@parsaaftabi)

@parsaaftabi

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

I do computers, all the way down.

I do computers, all the way down.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.