Re: function signature specialization crashlog
Re: function signature specialization crashlog
- Subject: Re: function signature specialization crashlog
- From: Torsten Curdt <email@hidden>
- Date: Mon, 31 Oct 2016 23:49:03 +0100
>
> > I have a real hard time understanding this iOS/Swift3 crashlog.
>
> This is an odd list to be posting this to. Crash logs are there for the
> developers
> of the crashing software. If you're interested in helping fix the
> compiler, that's great,
> but you should be bringing this up on swift-dev. If you're just trying to
> figure out how
> to get the Swift compiler to stop crashing on your code, the crash logs
> probably
> aren't going to help that much.
>
Hey John,
maybe this was misleading. It's from a crashlog from an iOS app - not the
compiler. I only tried to point out it was written in Swift3. But you might
be right and it's more a Swift question and therefor the wrong list.
My app crashed and I am trying to figure out what that crashlog means.
Given that I have no line numbers it's a bit of a guessing game.
And the error itself does not ring a bell either yet.
Maybe I should also try on the Swift IRC channel.
Thanks for that input.
> For one the closure #s do not help that very much (I just assume they
> numbered
> > from the beginning of the file?)
>
> They should be numbered from the beginning of the enclosing entity: in this
> case, the enclosing method.
>
Ah. OK. Wish I could have Xcode show me those numbers.
> and the closure line numbers are all 0.
>
> That's probably because it's implicitly-generated code.
>
Hm. What is implicit about that closure code?
I wrote it and hence it should have line numbers.
cheers,
Torsten
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden