You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
SIGTRAP in drop glue when slice literal initialization panics #30018
Yeah, when compiling with optimizations, it won't hit this signal but continues on and behavior depends on the specific case. The minimized example exits without issue, but the test case I had in my crate segfaults.
I think I know why this happens; it is probably related to how somewhat sloppy handling of the drop flags on scratch/temporary values in other contexts (see e.g. #30530).
Activity
sfackler commentedon Nov 24, 2015
Popped up in broken tests in one of my crates: kornelski/rust-security-framework@8ab48c2
alexcrichton commentedon Nov 25, 2015
triage: I-nominated
probably good to have crashes like this categorized at least
sfackler commentedon Nov 25, 2015
It does appear to have been present since 1.0 at least, BTW.
sfackler commentedon Nov 25, 2015
@alexcrichton added back I-nominated, assuming that the removal was unintentional.
nikomatsakis commentedon Dec 3, 2015
@pnkfelix notes that this is likely a debug flag, and probably only occurs if debug assertions are enabled.
nikomatsakis commentedon Dec 3, 2015
triage: P-medium
sfackler commentedon Dec 3, 2015
Yeah, when compiling with optimizations, it won't hit this signal but continues on and behavior depends on the specific case. The minimized example exits without issue, but the test case I had in my crate segfaults.
pnkfelix commentedon Jan 11, 2016
I think I know why this happens; it is probably related to how somewhat sloppy handling of the drop flags on scratch/temporary values in other contexts (see e.g. #30530).