Skip to content

[TypeReconstruction] Don't choke on slightly invalid mangled names. #17328

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

Merged
merged 1 commit into from
Jun 19, 2018

Conversation

dcci
Copy link
Member

@dcci dcci commented Jun 19, 2018

This was taken from a real project, but I don't have it anymore
and I can't reproduce it on newer versions of swift (probably
something changed in the DWARF type mangling). In any case, as
this can be triggered by user input, we shouldn't assert, and
error out instead.

rdar://problem/39283717

This was taken from a real project, but I don't have it anymore
and I can't reproduce it on newer versions of swift (probably
something changed in the DWARF type mangling). In any case, as
this can be triggered by user input, we shouldn't assert, and
error out instead.

<rdar://problem/39283717>
@dcci dcci requested review from slavapestov and fredriss June 19, 2018 18:39
@dcci
Copy link
Member Author

dcci commented Jun 19, 2018

@swift-ci please test and merge

@dcci
Copy link
Member Author

dcci commented Jun 19, 2018

FWIW, this gets demangled something weird, I don't think it's really valid, but cc:ing @eeckstein for confirmation

$S12EyeCandyCore11XPCListenerC14messageHandleryyAA13XPCConnectionV_AA10XPCMessageVxtcvpfiyAF_AHxtcfU_TA.4 ---> closure #1 (EyeCandyCore.XPCConnection, EyeCandyCore.XPCMessage, A) -> () in variable initialization expression of EyeCandyCore.XPCListener.messageHandler : (EyeCandyCore.XPCConnection, EyeCandyCore.XPCMessage, A) -> ()partial apply forwarder with unmangled suffix ".4"

@swift-ci swift-ci merged commit 7b3d6c0 into swiftlang:master Jun 19, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants