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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

rpm --initdb always segfault if there’s no existing databases #1846

Closed
ytrezq opened this issue Apr 2, 2017 · 4 comments
Closed

rpm --initdb always segfault if there’s no existing databases #1846

ytrezq opened this issue Apr 2, 2017 · 4 comments

Comments

@ytrezq
Copy link

ytrezq commented Apr 2, 2017

Please use the following bug reporting template to help produce actionable and reproducible issues. Please try to ensure that the reproduction is minimal so that the team can go through more bugs!

  • Actual results (with terminal output if applicable)
    core dump
  • Your Windows build number
    10.0.14393.447
  • Steps / All commands required to reproduce the error from a brand new installation
    install rpm with an rpm based distribution (not the default shipped ubuntu) and create /var/lib/rpm as root.
    Then just create an empty database with rpm --initdb
  • Strace of the failing command
    due to Please support disabling address space load randomization for individual processes. #1148 I can’t use the strace command.
@stehufntdev
Copy link
Collaborator

Thanks for reporting the issue. #1148 shouldn't impact strace, can you please clarify that part? Also, could you give this a try in the Creator's update since there have been a number of fixes since the Anniversary build including #1148.

@ytrezq
Copy link
Author

ytrezq commented Jul 18, 2017

@stehufntdev : In fedora, all executables are address independant, so this impact strace.
I confirm this affect10.0.16232. I also confirm I can no longer install strace because of this.

@craigloewen-msft
Copy link
Member

Can you please try this on a more recent build and re-open if you still hit this issue. Thanks!

@therealkenc
Copy link
Collaborator

The OP was running an unsupported distribution (Fedora) which is why this one went chirping crickets. The problem is almost certainly variation "mmap's problems" and will likely suffer in current releases like ref #3493.

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

No branches or pull requests

4 participants