[SR-3207] Segfault with Obj-C parameter of (NSError* __autoreleasing __nonnull * __nullable) #45795
Comments
|
We should probably just refuse to import this as a throwing method at all. |
|
That said, the Swift compiler shouldn't really be responsible for diagnosing Objective-C mistakes. Unfortunately, Objective-C doesn't really have a way to know that this is a mistake, but maybe a warning would be okay anyway. |
|
Comment by David Sweeris (JIRA) This is probably one of those noob questions... How do you get swift to import objc stuff from the command line? All but one of the resources I could find on the topic assume you're compiling with Xcode, and I just can't find the incantation to pass to swift to even get this to even try to compile. Right now, under "Arguments Passed On Launch", I've got "-frontend -c /path/to/main.swift -import-objc-header /path/to/SegFaulter-Bridging-Header.h /path/to/MyObject.m -F /System/Library/Frameworks/Foundation -I/usr/include", and the output is: /path/to/SegFaulter-Bridging-Header.h:1:9: note: in file included from /path/to/SegFaulter-Bridging-Header.h:1:
#import "MyObject.h"
^
/path/to/MyObject.h:1:9: error: module 'Foundation' not found
@import Foundation;
^
<unknown>:0: error: failed to import bridging header '/path/to/SegFaulter-Bridging-Header.h'
Program ended with exit code: 1 |
|
That's pretty much it, but -F is a search path option, so you want to point it at the directory that contains frameworks. …wait, why do you have a .m file in there? |
|
Comment by David Sweeris (JIRA) Do the .m files not need to be compiled? The output is the same if I remove it. |
AnthonyLatsis
added
the
crash
Attachment: Download
Environment
Xcode 8.1 (8B62), command line app template (attached)
Additional Detail from JIRA
md5: a83cf30f388c234c30c5851dc159b2e4
is duplicated by:
Issue Description:
With the following setup:
MyObject.h:
MyObject.m:
main.swift
Compilation gets the following crash:
The issue appears to be that the
__nullableand__nonnullannotations are transposed, which is an easy mistake to make. The compiler should warn, error, and/or provide a fix-it, rather than crashing.The text was updated successfully, but these errors were encountered: