You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Starting with the 08-29-2021 nightly snapshot (the 08-28-2021 nightly did not exhibit this), the following simple function:
func crasher(arg:Any=Void()){}
placed by itself in a file triggers the assertion failure of "(Range.isValid() && "range should be valid"), function extractText, file SourceLoc.cpp, line 229" when generating debug symbols (swiftc -g file.swift).
As mentioned above, this appears to have happened at some point between the 08-28-2021 and 08-29-2021 nightly snapshots, but I have not yet isolated this further.
theindigamer (JIRA User) - I still had seen it this morning with last night's nightly Swift.org toolchain (the Sept. 14 one), but hadn't built one newer than that yet. This does only happen with `swiftc -g`, not plain `swiftc`, in case you'd tried the latter. I can try with a newer build, though.
Additional Detail from JIRA
md5: 76521cafbc87c7e5766c3168ca608eaa
Issue Description:
Starting with the 08-29-2021 nightly snapshot (the 08-28-2021 nightly did not exhibit this), the following simple function:
placed by itself in a file triggers the assertion failure of "(Range.isValid() && "range should be valid"), function extractText, file SourceLoc.cpp, line 229" when generating debug symbols (swiftc -g file.swift).
As mentioned above, this appears to have happened at some point between the 08-28-2021 and 08-29-2021 nightly snapshots, but I have not yet isolated this further.
The full stack trace is as follows:
The text was updated successfully, but these errors were encountered: