# Rust Debugging Quest

**URL:** <https://internals.rust-lang.org/t/rust-debugging-quest/6753>\
**Category:** tools and infrastructure\
**Created:** [February 12, 2018, 9:27pm UTC](https://internals.rust-lang.org/t/rust-debugging-quest/6753 "2018-02-12T21:27:19Z")\
**Posts on this page:** 1\
**Showing post:** 19

<div class="post-metadata">

**Author:** ![gilescope](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/gilescope/32/2798_2.png) [@gilescope](https://internals.rust-lang.org/u/gilescope)\
**Post date:** [March 27, 2019, 8:09am UTC](https://internals.rust-lang.org/t/rust-debugging-quest/6753/19 "2019-03-27T08:09:45Z")

</div>

I think the current state is a new effort is needed:

> [@How to support Rust debugging post-Tromey?](https://internals.rust-lang.org/t/how-to-support-rust-debugging-post-tromey/9207):
>
> So, I’m sorry to say it but @tromey will be started a new job come next Thursday and likely won’t have time to help with Rust debugging anymore. We need to discuss how we are going to maintain the current Rust debuginfo support. I had a few thoughts: Would there be interest in @tromey doing a kind of “intro to debugging support” talk? I was thinking we could do a video call where @tromey walks through how debuginfo works, where rust-lldb lives, etc. We could record it, too, for others to watch…

---

_[View the full topic](https://internals.rust-lang.org/t/rust-debugging-quest/6753)._