Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[SR-4853] Compiler assertion in recent snapshot. #47430

Open
swift-ci opened this issue May 10, 2017 · 3 comments
Open

[SR-4853] Compiler assertion in recent snapshot. #47430

swift-ci opened this issue May 10, 2017 · 3 comments

Comments

@swift-ci
Copy link
Collaborator

@swift-ci swift-ci commented May 10, 2017

Previous ID SR-4853
Radar None
Original Reporter maik (JIRA User)
Type Bug
Environment

Swift snapshot from May 9, 2017 and Xcode 8.3.2

Additional Detail from JIRA
Votes 1
Component/s Compiler
Labels Bug, CompilerCrash
Assignee None
Priority Medium

md5: 2a0f7f3f25c710a66eafc5658b998e33

relates to:

  • SR-4850 Assertion failed: (Val && "isa<> used on a null pointer"), function doit

Issue Description:

The compiler will generate the following assertion both in Debug and Single-File-Optimization mode. If WMO is checked, then the build will succeed.

Assertion failed: (Val && "isa<> used on a null pointer"), function doit, file /Users/buildnode/jenkins/workspace/oss-swift-package-osx/llvm/include/llvm/Support/Casting.h, line 95.
0  swift                    0x0000000108918998 llvm::sys::PrintStackTrace(llvm::raw_ostream&) + 40
1  swift                    0x0000000108917966 llvm::sys::RunSignalHandlers() + 86
2  swift                    0x0000000108918f59 SignalHandler(int) + 361
3  libsystem_platform.dylib 0x00007fff8ca36b3a _sigtramp + 26
4  libsystem_platform.dylib 000000000000000000 _sigtramp + 1935447264
5  libsystem_c.dylib        0x00007fff8c8bb420 abort + 129
6  libsystem_c.dylib        0x00007fff8c882893 basename_r + 0
7  swift                    0x00000001062f2149 swift::ModuleFile::finishNormalConformance(swift::NormalProtocolConformance*, unsigned long long) + 4249
8  swift                    0x000000010674a6e3 swift::NormalProtocolConformance::resolveLazyInfo() const + 99
9  swift                    0x0000000106324d95 swift::serialization::Serializer::writeNormalConformance(swift::NormalProtocolConformance const*) + 661
10 swift                    0x000000010633340b swift::serialization::Serializer::writeAllDeclsAndTypes() + 2699
11 swift                    0x0000000106334898 swift::serialization::Serializer::writeAST(llvm::PointerUnion<swift::ModuleDecl*, swift::SourceFile*>, bool) + 3288
12 swift                    0x000000010633955b swift::serialization::Serializer::writeToStream(llvm::raw_ostream&, llvm::PointerUnion<swift::ModuleDecl*, swift::SourceFile*>, swift::SILModule const*, swift::SerializationOptions const&) + 139
13 swift                    0x000000010636a0e3 void llvm::function_ref<void (llvm::raw_ostream&)>::callback_fn<swift::serialize(llvm::PointerUnion<swift::ModuleDecl*, swift::SourceFile*>, swift::SerializationOptions const&, swift::SILModule const*)::$_4>(long, llvm::raw_ostream&) + 179
14 swift                    0x000000010633a6eb withOutputFile(swift::ASTContext&, llvm::StringRef, llvm::function_ref<void (llvm::raw_ostream&)>) + 395
15 swift                    0x000000010633a4dc swift::serialize(llvm::PointerUnion<swift::ModuleDecl*, swift::SourceFile*>, swift::SerializationOptions const&, swift::SILModule const*) + 220
16 swift                    0x000000010571728c performCompile(swift::CompilerInstance&, swift::CompilerInvocation&, llvm::ArrayRef<char const*>, int&, swift::FrontendObserver*, swift::UnifiedStatsReporter*) + 10428
17 swift                    0x00000001057138fa swift::performFrontend(llvm::ArrayRef<char const*>, char const*, void*, swift::FrontendObserver*) + 2650
18 swift                    0x00000001056d03a0 main + 3312
19 libdyld.dylib            0x00007fff8c827235 start + 1
20 libdyld.dylib            0x000000000000003c start + 1937608200

The path to the file is also strange, as there is no such user on my system.

Unfortunately I cannot share the project.

@belkadan
Copy link
Contributor

@belkadan belkadan commented May 10, 2017

Can you at least give the information at the end of the stack trace? (The "While…" part.) Otherwise I'm afraid we'll have to close this out as insufficient information.

@swift-ci
Copy link
Collaborator Author

@swift-ci swift-ci commented May 10, 2017

Comment by Maik Bastian (JIRA)

There seems to be no "while" part. Only the program arguments are printed after the stack trace.

@belkadan
Copy link
Contributor

@belkadan belkadan commented May 10, 2017

Hm, okay. Guess we should add more tracing on our side.

@swift-ci swift-ci transferred this issue from apple/swift-issues Apr 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants