• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: function signature specialization crashlog
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: function signature specialization crashlog


  • Subject: Re: function signature specialization crashlog
  • From: John McCall <email@hidden>
  • Date: Mon, 31 Oct 2016 16:09:06 -0700

> On Oct 31, 2016, at 3:49 PM, Torsten Curdt <email@hidden> wrote:
>
> > 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.

I see.  If it's a crash in running code, that's different.

> 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.

From the information there, I would guess that maybe the closure has been released or corrupted.

> 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.

If it helps, it looks like:

 - you're calling a function with the signature ([Foo.Store], CLLocation?, CLLocation?, Bool) throws -> [Foo.Store]
 - that function is calling another closure
 - that closure is crashing

> > 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.

The code is at least wrapped with some implicit code, and it may be that code which is crashing.

John.
_______________________________________________

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


  • Follow-Ups:
    • Re: function signature specialization crashlog
      • From: Torsten Curdt <email@hidden>
References: 
 >function signature specialization crashlog (From: Torsten Curdt <email@hidden>)
 >Re: function signature specialization crashlog (From: John McCall <email@hidden>)
 >Re: function signature specialization crashlog (From: Torsten Curdt <email@hidden>)

  • Prev by Date: Re: function signature specialization crashlog
  • Next by Date: Re: function signature specialization crashlog
  • Previous by thread: Re: function signature specialization crashlog
  • Next by thread: Re: function signature specialization crashlog
  • Index(es):
    • Date
    • Thread