-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
osmscout-server-gui segfaults on startup #377
Comments
Few questions:
Try to run in these conditions.
In general, is it easy to get NixOS in the virtual machine for testing/debugging? Anything special in DBus session handling on NixOS? |
It's already a debug build (and linking against a debug build of qt).
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.
I'll try this next.
In theory, yes. In practice, there might be quite a steep learning curve if you're only used to more conventional linuxes.
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 |
Updating to osmscout-server version 2.0.1, built against Qt 5.15.2 on NixOS, I get a segfault on startup:
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: onlyosmscout-server-gui
crashes.The text was updated successfully, but these errors were encountered: