Modular•13mo ago

Has anyone ever seen this error

While I was writing out some code on mojo, this error message appeared on the first line of my code.

A crash happened in the Mojo Language Server when processing this document. The Language Server will try to reprocess this document once it is edited again. Please report this issue in https://github.com/modularml/mojo/issues along with all the relevant source codes with their current contents.

A crash happened in the Mojo Language Server when processing this document. The Language Server will try to reprocess this document once it is edited again. Please report this issue in https://github.com/modularml/mojo/issues along with all the relevant source codes with their current contents.

Afterwards, regardless of the changes I make (ie making a new file or altering current file) I keep getting the following error and stack dump:

Stack dump without symbol names (ensure you have llvm-symbolizer in your PATH or set the environment var

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):

 to point to it):

After spitting out a couple hundred messages identical to

255 mojo      0x000057bc2c289433

255 mojo      0x000057bc2c289433

The output finally crashes

mojo crashed!
Please file a bug report.
Segmentation fault (core dumped)

mojo crashed!
Please file a bug report.
Segmentation fault (core dumped)

I've already put this into github but was wondering if anyone knows what this is, what I did to cause it, and how to fix it. Thank you

Cchristian_drake While I was writing out some code on mojo, this error message appeared on the fi...

Robert•12/18/24, 2:53 AM

Yep a couple of times. Some are segmentation faults. Mine have been software compatibility issues with symbolic links eg libraries or packages not optimally installed in my environment. LLVM afaik goes back to the compiler and has to do with MLIR and that stuff. I think this is good. We are benchmarking the Mojo kernel

RRobert Yep a couple of times. Some are segmentation faults. Mine have been software com...

christian_drakeOP•12/18/24, 4:58 AM

Thanks for the update, I thought these might be because mojo is a young language. I'm assuming I just need to create a new mojo project.

Cchristian_drake Thanks for the update, I thought these might be because mojo is a young language...

Robert•12/18/24, 5:38 AM

btw and i hope the Modular team reads this. Some of these technical issues is also with software from way larger companies as well not just this stack which says alot. Like alot.

ModularBot•12/18/24, 5:40 AM

Congrats @christian_drake, you just advanced to level 2!

Darkmatter•12/18/24, 11:57 AM

I would try installing clang. I’ve found that usually carries versions of any missing LLVM deps.