You have a stack dump, which means you will get all the information if you symbolicate your crash report. Xcode can do it for you automatically, but some manual methods also exist.

Indeed the error report being complained about explains this and tells you how to fix it.

Maybe the friendly default would be to have the symbolicated reports on, but perhaps this has performance impact so it’s off.

> Maybe the friendly default would be to have the symbolicated reports on

As a comment just below says, the solution is quite simple:

> ensure you have llvm-symbolizer in your PATH or set the environment var `LLVM_SYMBOLIZER_PATH` to point to it

Here is the output with the environment variable set.

https://pastebin.com/8M9Dbrgj

This doesn't provide anything useful either.

Seems like there's an architecture error or something, the last line indicates you might have an error with the flag:

> zsh: illegal hardware instruction LLVM_SYMBOLIZER_PATH=/usr/local/opt/llvm/bin/llvm-symbolizer swift main.swift

that's not related to the symbolizer thing. It seems to just be part of the "index out of range" crash. I get the same thing without using the symbolizer.

    zsh: illegal hardware instruction  swift main.swift

Ouch, and yuk. I stand corrected!

I am getting proper error feedback,

``` swift_hello_main + 322 in swift-hello at /home/fermi/Documents/temp/swift-hello/Sources/main.swift:64:8

    62│
    63│ let a = [1]
    64│ print(a[1])
      │        ▲
    65│

```

What if you follow the advice here

>Stack dump without symbol names (ensure you have llvm-symbolizer in your PATH or set the environment var `LLVM_SYMBOLIZER_PATH` to point to it):

?

What if the error was more descriptive out of the box? Unless of course the goal is to just compete with C++ error reporting.

The goal is to probably avoid duplicating efforts when llvm-symbolize already exists.

There’s obviously a snarky comment to make here about Go developers and duplicating efforts.

If I follow the advice

https://pastebin.com/8M9Dbrgj

Not sure how that's any better... I still have no idea that the error occurred on line 2

The Swift REPL sucks for this. I would suggest you compile to a binary and use your normal debugging tools.

Swift outside of Xcode is a bit rough around the edges, I think because more attention goes into making Xcode friendly. I opened Xcode, made a new playground, and hit run, the code crashes and highlights the line where the error occurred in red. Not to excuse Swift's jankyness, just saying that the kind of default experience is more an IDE-first design compared to Go's very good unix-first design.

https://monosnap.com/file/qhlwD6aXUW5bcl3TV5lPmKFDgjWDtD

I'm just curious, if I was to run my application on a linux server.

How would I ever know what caused the crash?

when I compile using `swiftc main.swift` and run with `./main`, the error seems even more useless.

all I get is:

    Swift/ContiguousArrayBuffer.swift:600: Fatal error: Index out of range
    zsh: illegal hardware instruction  ./main

I don't know, I write Swift on a Mac targeting macOS or iOS. I usually have Xcode open to build/run/debug and for documentation lookup, and alternate between that and VSCode for actually writing the code; worst thing about Xcode for me is the find-replace, that's probably the biggest reason I keep VSCode open.

You can load the coredump into GDB.

Yea because kotlin without a jetbrains ide is such a good experience.

At least the jetbrains ide exists for all major platforms.

Verbosity. That's..... yap-ple!