Determining if a crash is a known issue?


(Lily Ballard) #1

When I get a crash in Swift, is there any easy way to figure out if it's already a known crasher? I know there's a bunch of test cases in validation-test/compiler_crashers{,_2}/ which I assume are all existing crashers. Short of reading through them for similar-looking code, is there some solution? Ideally I'd be able to take the stack trace for my crash and correlate it against stack traces for the known crashers.

-Kevin Ballard


(Greg Parker) #2

When I get a crash in Swift, is there any easy way to figure out if it's already a known crasher?

Not that I know of.

I know there's a bunch of test cases in validation-test/compiler_crashers{,_2}/ which I assume are all existing crashers.

They are not. They are crashes collected by https://github.com/practicalswift/swift-compiler-crashes . Some were discovered by users, most were discovered by automated fuzzers, and there are often duplicates among them.

ยทยทยท

On Dec 9, 2015, at 1:56 PM, Kevin Ballard via swift-dev <swift-dev@swift.org> wrote:

--
Greg Parker gparker@apple.com Runtime Wrangler