Mirror of forum.nim-lang.org

8145 :: Stack trace of runtime errors will be the path of the developer's PC.

• nnahito (orginal) [2021-06-23T11:18:30+02:00] view original

  The user folder name on my PC is "nnahito".

  I created software in the Nim language, did exe compilation, and distributed it.

  One day, a user sent me a screenshot of a runtime error. There is find the stack trace information. I had not written try...catch, so the exceptions were written as they were.

  And there it was, my user directory name "nnahito". Of course, that user does not have a directory named nnahito.

  How could this have happened? If this is the case, I will not be able to distribute the software I have created. Please tell me how to fix it.

  Thank you very much.

---

• haxscramper (orginal) [2021-06-23T11:34:44+02:00] view original

  Exception stacktrace has nothing to do with your user's paths, so it is perfectly natural for it to show your original code. If you want to modify stacktrace information (print paths differently for example) you can manually get all stack trace entries from an exception using https://nim-lang.org/docs/system.html#getStackTraceEntries%2Cref.Exception

---

• Yardanico (orginal) [2021-06-23T11:36:34+02:00] view original

  The best way would be to only ship binaries compiled in release mode (-d:release).

  But if you really want to only disable full paths without anything else, you can use --excessiveStackTrace:off.

---

• nnahito (orginal) [2021-06-23T11:49:40+02:00] view original

  Thank you for your answer. I have switch("d", "release") in config.nims, but Doesn't this make it a release build?

---

• nnahito (orginal) [2021-06-23T11:50:51+02:00] view original

  Thank you for your answer. So it is natural that the path of the developer's PC is displayed? I didn't know that. Thank you very much.

---

• Yardanico (orginal) [2021-06-23T11:57:15+02:00] view original

  It does, but only on the latest version which is 1.4.8. If you're on an older version, update or use -d:release in the command line when building the binary.

---