Skip to content

Docs on bugreporting should elaborate on creating a stack trace #19745

Closed
@untitaker

Description

@untitaker

http://doc.rust-lang.org/complement-bugreport.html#what-information-should-i-include-in-a-bug-report?

Finally, if you can run the offending command under gdb, pasting a stack trace can be useful; to do so, you will need to set a breakpoint on rust_panic.

This doesn't explain anything to me, but a short added explanation probably won't suffice either.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions