lagrange: Crash building Lagrange from source without installing system wide with older Lagrange installed system wide
Current main
Thread 1 "lagrange" received signal SIGSEGV, Segmentation fault.
0x0000aaaaaaad3c50 in load_Lang_ (d=0xaaaaaac034e0 <lang_>, id=0xaaaaaabaa380 "en") at /home/alyssa/lagrange/src/lang.c:128
128 while (*++ptr) {}
(gdb) bt
#0 0x0000aaaaaaad3c50 in load_Lang_ (d=0xaaaaaac034e0 <lang_>, id=0xaaaaaabaa380 "en") at /home/alyssa/lagrange/src/lang.c:128
#1 0x0000aaaaaaad3db0 in setCurrent_Lang (language=0xaaaaaabaa380 "en") at /home/alyssa/lagrange/src/lang.c:159
#2 0x0000aaaaaaad3d44 in init_Lang () at /home/alyssa/lagrange/src/lang.c:147
#3 0x0000aaaaaaab0ca4 in init_App_ (d=0xaaaaaac03160 <app_>, argc=1, argv=0xfffffffff878) at /home/alyssa/lagrange/src/app.c:682
#4 0x0000aaaaaaab2eb0 in run_App (argc=1, argv=0xfffffffff878) at /home/alyssa/lagrange/src/app.c:1531
#5 0x0000aaaaaaaae300 in main (argc=1, argv=0xfffffffff878) at /home/alyssa/lagrange/src/main.c:78
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 15 (15 by maintainers)
Commits related to this issue
- App: resources.lgr load order Try loading from the local directory first, then the system-wide one. This way uninstalled builds are more likely to use the right resources. IssueID #363 — committed to skyjake/lagrange by skyjake 3 years ago
- Changed format of resources.lgr Resources are now stored in a ZIP archive, and it comes with an explicit version number. All the old embed/bincat stuff was removed as unnecessary. resources.lgr is a... — committed to skyjake/lagrange by skyjake 3 years ago
To summarize reproduction steps – install old Lagrange so that /usr/local/share/lagrange/resources.lgr exists, build new Lagrange without installing and try to run from the build directory. Due to a version mismatch this will segfault.