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

ASAN: Installed Version of `kdb` Fails If Address Sanitizer is Enabled #1569

Open
sanssecours opened this Issue Aug 7, 2017 · 3 comments

Comments

Projects
None yet
2 participants
@sanssecours
Contributor

sanssecours commented Aug 7, 2017

Steps to Reproduce

  1. Clone this repository

  2. Create a build directory and change into this build directory

    mkdir build
    cd build
  3. Create the build system

    cmake -GNinja -DENABLE_ASAN=ON ..
  4. Install Elektra

    ninja install 
  5. Run kdb

    kdb

Expected Result

The command kdb shows a list of subcommands.

Actual Result

The command displays the following error message:

Usage: kdb <command> [args]

kdb is a program to manage elektra's key database.
Please run a command with -H or --help as args to show a help text for
a specific command.

Known commands are:
Sorry, I have a severe problem, it seems like I am not installed correctly!
kdbOpen() failed with the info:
 Sorry, 1 warning was issued ;(
 Warning (#1):
	Description: could not load module, dlopen failed
	Ingroup: modules
	Module: dl
	At: ../src/libs/loader/dl.c:88
	Reason: of module: libelektra-resolver.so, because: (null)
	Mountpoint:
	Configfile:
Sorry, the error (#40) occurred ;(
Description: failed to open default backend (see warnings for more information)
Ingroup: kdb
Module:
At: ../src/libs/elektra/kdb.c:287
Reason: could not open default backend
Mountpoint:
Configfile:

Please report the issue at https://issues.libelektra.org/

System Information

  • Elektra Version: master
  • OS: macOS 10.12.6

@sanssecours sanssecours added this to the 1.0.0 milestone Aug 7, 2017

@markus2330

This comment has been minimized.

Show comment
Hide comment
@markus2330

markus2330 Aug 7, 2017

Contributor

Thank you for reporting!

Is this really relevant for 1.0.0?

Contributor

markus2330 commented Aug 7, 2017

Thank you for reporting!

Is this really relevant for 1.0.0?

@sanssecours

This comment has been minimized.

Show comment
Hide comment
@sanssecours

sanssecours Aug 7, 2017

Contributor

Is this really relevant for 1.0.0?

Not really, but since the issue is not really relevant for 0.8.20 either, I just selected the release farthest away in the future 😊.

Contributor

sanssecours commented Aug 7, 2017

Is this really relevant for 1.0.0?

Not really, but since the issue is not really relevant for 0.8.20 either, I just selected the release farthest away in the future 😊.

@markus2330 markus2330 removed this from the 1.0.0 milestone Aug 10, 2017

@markus2330

This comment has been minimized.

Show comment
Hide comment
@markus2330

markus2330 Aug 10, 2017

Contributor

It is okay that issues do not have a milestone if they are not urgent at all. I think this is the case here.

Contributor

markus2330 commented Aug 10, 2017

It is okay that issues do not have a milestone if they are not urgent at all. I think this is the case here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment