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.

Sign up for GitHub

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

Jump to bottom

[SR-12610] Dictionary crashes with CMTime keys #55054

Open
iby opened this issue Apr 16, 2020 · 2 comments
Open

[SR-12610] Dictionary crashes with CMTime keys #55054

iby opened this issue Apr 16, 2020 · 2 comments
Labels
bug A deviation from expected or documented behavior. Also: expected but undesirable behavior.

Comments

@iby
Copy link

iby commented Apr 16, 2020

Previous ID SR-12610
Radar rdar://problem/62202402
Original Reporter @iby
Type Bug

Attachment: Download

Additional Detail from JIRA
Votes 0
Component/s
Labels Bug
Assignee None
Priority Medium

md5: 700c248ceec4136ca0058efa14d18636

Issue Description:

I have an internal static framework with tests and a demo app – everything works great. Inside the main app in a separate project (after updating to Swift 5.2 and Xcode 11.4) I'm getting a crash where the aforementioned framework uses the following line:

```
Swift.print([CMTime(value: 1, timescale: 600): 1.0])
```

  • `CMTime` on it's own works just fine.

  • `Dictionary` with built-in types also works fine.

  • `Dictionary` with `CMTime` as value works fine!

  • `Dictionary` with `CMTime` as key goes EXC_BAD_ACCESS!

See the screenshot below.

P.S. I'm using `CLANG_MODULES_AUTOLINK` to automatically link referenced libraries. If I link it explicitly, everything also works. Has anything changed in 5.2 that doesn't play nicely with auto-linking? Or is this a separate problem?
@beccadax
Copy link
Contributor

@swift-ci create

@eeckstein
Copy link
Member

@iby Is it possible that you attach a self-contained test case?

@swift-ci swift-ci transferred this issue from apple/swift-issues Apr 25, 2022
@iby iby mentioned this issue Apr 11, 2023
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug A deviation from expected or documented behavior. Also: expected but undesirable behavior.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@beccadax @iby @eeckstein