# Mojo errors dropping into MLIR — how do you deal with this?
**URL:** https://forum.modular.com/t/mojo-errors-dropping-into-mlir-how-do-you-deal-with-this/2999
**Category:** Mojo
**Created:** [April 24, 2026, 10:41pm UTC](https://forum.modular.com/t/mojo-errors-dropping-into-mlir-how-do-you-deal-with-this/2999 "2026-04-24T22:41:40Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@Krun\_Dev](https://forum.modular.com/u/Krun_Dev)
#### Post date: [April 24, 2026, 10:41pm UTC](https://forum.modular.com/t/mojo-errors-dropping-into-mlir-how-do-you-deal-with-this/2999/1 "2026-04-24T22:41:40Z")
I’ve been running into this with Mojo lately: something breaks, and the error drops into MLIR instead of pointing to my code.
I’m not even talking about complex stuff — just normal code that looks fine, but the error feels disconnected. At that point I’m not debugging logic anymore, just guessing what the compiler did.
I get why MLIR is there, but right now it feels like the abstraction leaks too early.
How are you dealing with this?
- Do you just get used to reading these errors?
- Any workflow that actually helps?
- Or is this just where Mojo is right now?
Feels like a real DX pain for me.
---
### Author:  [@owenhilyard](https://forum.modular.com/u/owenhilyard)
#### Post date: [April 24, 2026, 11:01pm UTC](https://forum.modular.com/t/mojo-errors-dropping-into-mlir-how-do-you-deal-with-this/2999/2 "2026-04-24T23:01:14Z")
All of those should be reported as bugs (ideally with minimal reproducers). Unless you’re doing fairly low level things (ex: touching MLIR directly) you shouldn’t see that and we treat that as one level of severity worse than the compiler segfaulting.
---
### Author:  [@clattner](https://forum.modular.com/u/clattner)
#### Post date: [April 25, 2026, 2:45pm UTC](https://forum.modular.com/t/mojo-errors-dropping-into-mlir-how-do-you-deal-with-this/2999/3 "2026-04-25T14:45:21Z")
Can you give an example of what you’re seeing?