Rust Debugging

What it does

The rust-debugging skill assists in identifying and resolving issues within Rust code. It can analyze error messages, suggest potential causes for panics or unexpected behavior, and provide guidance on using debugging tools like gdb or the built-in debugger. This skill is particularly useful for developers working with low-level systems programming concepts where errors can be subtle and difficult to track down.

When to use it

• Analyzing Panic Messages: You're encountering a panic during runtime and need help understanding the root cause from the stack trace.
• Debugging Memory Safety Issues: You suspect memory corruption or borrowing issues but are unsure how to pinpoint the exact location of the problem.
• Understanding Complex Errors: A compiler error message is cryptic, and you need assistance interpreting it and suggesting fixes.
• Using Debugging Tools: You want help setting up and using gdb or other debugging tools for Rust code.

Key capabilities

• Error Message Analysis
• Panic Stack Trace Interpretation
• Memory Safety Issue Identification
• Debugging Tool Guidance (e.g., gdb)

Example prompts

• "I'm getting a panic in my Rust program: thread 'main': called result.downcast_ref() on Result::Err. What could be causing this?"
• "Can you explain the following compiler error: cannot move out of borrowed content?"
• "How do I use gdb to debug a Rust binary?"

Tips & gotchas

This skill assumes a basic understanding of Rust syntax and concepts. Providing relevant code snippets or error messages will significantly improve the quality of its suggestions.