osmscout-server
osmscout-server copied to clipboard
osmscout-server-gui segfaults on startup
Updating to osmscout-server version 2.0.1, built against Qt 5.15.2 on NixOS, I get a segfault on startup:
> osmscout-server-gui
Failed to load translation for "en_GB" ":/i18n"
/tmp/nix-shell-28327-0/rc: line 1: 30086 Segmentation fault (core dumped) osmscout-server-gui
Backtrace from the coredump: gdb.txt. Doesn't look super informative, as it's entirely Qt code on the stack, so I can't tell at a glance which bit of qml it was trying to load.
Let me know if there's anything you'd like me to try (I can probably upload the coredump is that's helpful?).
osmscout-server
appears to run fine: only osmscout-server-gui
crashes.
Few questions:
- can you try to build debug version?
CONFIG+=debug
at qmake should result in it. - start GUI without server running
Try to run in these conditions.
- if fails, try to comment out https://github.com/rinigus/osmscout-server/blob/master/gui/src/servercontroller.cpp#L37 . That should disable any init code for starting server itself. It should show GUI with plain window stating that it tries to connect. Or does it crash in this case as well?
In general, is it easy to get NixOS in the virtual machine for testing/debugging?
Anything special in DBus session handling on NixOS?
- can you try to build debug version?
CONFIG+=debug
at qmake should result in it.
It's already a debug build (and linking against a debug build of qt).
- start GUI without server running
I tried this early on. It doesn't appear to make any difference whether the server is running. I don't believe the server was running when I captured the backtrace.
- if fails, try to comment out https://github.com/rinigus/osmscout-server/blob/master/gui/src/servercontroller.cpp#L37 . That should disable any init code for starting server itself. It should show GUI with plain window stating that it tries to connect. Or does it crash in this case as well?
I'll try this next.
In general, is it easy to get NixOS in the virtual machine for testing/debugging?
In theory, yes. In practice, there might be quite a steep learning curve if you're only used to more conventional linuxes.
Anything special in DBus session handling on NixOS?
Not that I'm aware off, but there may be.
I will wait for your results before diving into NixOS debugging. As there is vbox image, I could start that easily. But let's see if you manage to narrow down what is causing the crash