Skip to content

Cannot tell apart panic!() and assert!(false, "") in macro_backtrace() #82157

Open
@Aurel300

Description

@Aurel300

The two expressions:

panic!(); // A
assert!(false, "msg"); // B

Used to result in distinct macro_backtrace(). After updating to nightly-2021-02-14 (and I guess since #80851), the backtrace for both is identical, both listing the calls ["std::panic::panic_2015", "std::panic"].

IIUC, the latter should contain an additional core::assert or std::assert item in the backtrace.

Meta

rustc --version --verbose:

rustc 1.52.0-nightly (5fa22fe6f 2021-02-14)
binary: rustc
commit-hash: 5fa22fe6f821ac3801d05f624b123dda25fde32c
commit-date: 2021-02-14
host: x86_64-unknown-linux-gnu
release: 1.52.0-nightly
LLVM version: 11.0.1

Activity

jyn514

jyn514 commented on Feb 16, 2021

@jyn514
Member

@Aurel300 what do you mean by macro_backtrace? I can't find it in the docs for the standard library.

Aurel300

Aurel300 commented on Feb 16, 2021

@Aurel300
Author

@jyn514 Yep, sorry, I should have linked to it. Yes, it is the Span::macro_backtrace you linked.

added
A-macrosArea: All kinds of macros (custom derive, macro_rules!, proc macros, ..)
requires-nightlyThis issue requires a nightly compiler in some way.
on Feb 16, 2021
jyn514

jyn514 commented on Feb 16, 2021

@jyn514
Member
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-macrosArea: All kinds of macros (custom derive, macro_rules!, proc macros, ..)C-bugCategory: This is a bug.requires-nightlyThis issue requires a nightly compiler in some way.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @Aurel300@jyn514

        Issue actions

          Cannot tell apart panic!() and assert!(false, "") in macro_backtrace() · Issue #82157 · rust-lang/rust