Mirror of forum.nim-lang.org

9324 :: Illegal storage access

• bijinpanicker (orginal) [2022-07-24T09:42:16+02:00] view original

  > nim c main.nim
  SIGSEGV: Illegal storage access. (Attempt to read from nil?)
  Run

  On compilation, I get only this message.
  How can I find the source of error (Illegal storage access) in my code?
  

  Compiler Details

  Nim Compiler Version 1.6.6 [Windows: i386]
  Compiled at 2022-05-05
  Copyright (c) 2006-2021 by Andreas Rumpf
  
  active boot switches: -d:release
  Run

---

• sky_khan (orginal) [2022-07-24T16:56:47+02:00] view original

  If it happens when you try to compile, thats a bug in compiler. If you can share your code maybe somebody would help to locate the bug or you may try to compile compiler in debug mode to see where it crashes.

---

• jasonfi (orginal) [2022-07-24T17:52:26+02:00] view original

  Why are you running a 32-bit version of the compiler?

  Does this happen for a very minimal program, e.g. echo "hello world"?

  If not, try commenting out code in your program until you've narrowed down which line is causing the compiler to crash, and post that line here.

---

• jyapayne (orginal) [2022-07-24T18:15:08+02:00] view original

  You can try using

  import segfaults
  Run

  In your main nim file. It might be able to give you a traceback.

---

• Stefan_Salewski (orginal) [2022-07-24T21:28:58+02:00] view original

  import segfaults
  Run

  added to his main.nim source text can catch a compiler issue? I am surprised, but your reply got two likes, so it may indeed be true.

  >On compilation, I get only this message.

  For debugging the compiler, I found this: https://github.com/nim-lang/Nim/wiki/Debugging-the-compiler

---

• JPLRouge (orginal) [2022-07-24T23:55:00+02:00] view original

  Yesterday I also had a compilation message with version 1.6.6 it could no longer compile even a small example.

  I reloaded 1.6.4 everything worked perfectly. I deleted 1.6.6 then reloaded everything is back to normal. etc... ????

  I had reported the issue, but deleted it thinking it was mine.

---

• jyapayne (orginal) [2022-07-25T03:51:09+02:00] view original

  Actually, I misunderstood the docs. Importing the segfaults module allows you to catch a segfault like you would an exception.

  So you could do:

  import segfaults
  
  proc main() =
    try:
      doSegfault()
    except:
      echo "segfault caught!"
      echo getCurrentException().getStackTrace()
  Run

  But it looks like this may not help OP. It could also be a compiler segfault, which would happen before any code on his end gets executed.

  @bijinpanicker, can you share a minimum example that causes your issue?

---

• Akito (orginal) [2022-07-29T02:28:44+02:00] view original

  Importing the segfaults module allows you to catch a segfault like you would an exception.

  Though, I think I remember reading, that this is not intended and is just a side-effect, which is too often exploited. Additionally, segfaults is considered broken.

  From my experience, you most of the time cannot catch segfaults, just because you imported that module.

---