Skip to content
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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

elektrad: crash on Debian Buster #3370

Open
markus2330 opened this issue Mar 17, 2020 · 1 comment
Open

elektrad: crash on Debian Buster #3370

markus2330 opened this issue Mar 17, 2020 · 1 comment
Assignees
Labels
bug

Comments

@markus2330
Copy link
Contributor

@markus2330 markus2330 commented Mar 17, 2020

Steps to Reproduce the Problem

Install golang-1.14-go (freshly arrived in backports 馃巻) and then compile and run elektrad:

PATH="$PATH:/usr/lib/go-1.14/bin" cmake -DTOOLS="kdb;web" . 
bin/elektrad

Expected Result

that elektrad starts successfully or prints some error message

Actual Result

panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x6b4ce7]

goroutine 1 [running]:
main.loadVersion()
        /home/markus/Projekte/Elektra/current/src/tools/web/elektrad/main.go:43 +0x37
main.main()
        /home/markus/Projekte/Elektra/current/src/tools/web/elektrad/main.go:17 +0x127

Backtrace:

Thread 1 "elektrad" received signal SIGSEGV, Segmentation fault.
main.loadVersion () at /home/markus/Projekte/Elektra/current/src/tools/web/elektrad/main.go:43
43              defer kdb.kdb.Close()
(gdb) bt
#0  main.loadVersion () at /home/markus/Projekte/Elektra/current/src/tools/web/elektrad/main.go:43
#1  0x00000000006b4ae7 in main.main () at /home/markus/Projekte/Elektra/current/src/tools/web/elektrad/main.go:17

System Information

  • Elektra Version: master
@mpranj

This comment has been minimized.

Copy link
Member

@mpranj mpranj commented Mar 17, 2020

@markus2330 thank you for testing and reporting. FYI I was only able to get it running in docker as described here, not on my host machine. It would be great if this could be improved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
You can鈥檛 perform that action at this time.