Bug 1249333 - dnf crash in select_next_target
Summary: dnf crash in select_next_target
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: dnf
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Packaging Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-08-01 17:14 UTC by Zbigniew Jędrzejewski-Szmek
Modified: 2015-08-11 14:18 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-08-11 14:18:02 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
bt full (98.21 KB, text/plain)
2015-08-01 17:14 UTC, Zbigniew Jędrzejewski-Szmek
no flags Details

Description Zbigniew Jędrzejewski-Szmek 2015-08-01 17:14:08 UTC
Created attachment 1058360 [details]
bt full

Description of problem:
Core was generated by `/usr/bin/python3 -OO /bin/dnf install qt5-qtbase-devel'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  select_next_target (err=<optimized out>, selected_full_url=<synthetic pointer>, 
    selected_target=<synthetic pointer>, dd=0x7ffcf8b71090)
    at /usr/src/debug/librepo/py3/librepo/downloader.c:667
667             if (target->state != LR_DS_WAITING)  // Pick only waiting targets

Version-Release number of selected component (if applicable):
dnf-1.0.2-2.fc24.1.noarch
librepo-1.7.16-2.fc23.x86_64
python3-3.4.3-5.fc23.x86_64

How reproducible:
reproducible

Comment 1 Zbigniew Jędrzejewski-Szmek 2015-08-01 18:39:57 UTC
> reproducible
dnf crashes ~60% of the time in this container, but in different places. So it seems to be some memory corruption issue.

Comment 2 Michal Luscon 2015-08-11 13:00:58 UTC
Hi,

are you able to provide us a coredump with the exact versions of dnf, hawkey and librepo? Do you experience this only in containerized environment?

Comment 3 Zbigniew Jędrzejewski-Szmek 2015-08-11 14:18:02 UTC
I cannot reproduce this anymore. Unfortunately I have upgrade dnf to dnf-1.0.2-3.fc24.noarch in the mean time which might be related, but again might not.


Note You need to log in before you can comment on or make changes to this bug.