Bug 1268107 - valgrind error on exit from ipython3
valgrind error on exit from ipython3
Product: Fedora
Classification: Fedora
Component: librepo (Show other bugs)
x86_64 Linux
unspecified Severity low
: ---
: ---
Assigned To: Tomas Mlcoch
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2015-10-01 16:31 EDT by Orion Poplawski
Modified: 2016-12-20 09:50 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2016-12-20 09:50:43 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Orion Poplawski 2015-10-01 16:31:21 EDT
Description of problem:

valgrind ipython3

==19187== Invalid read of size 8
==19187==    at 0x233C9E5D: exit_librepo (librepomodule.c:133)
==19187==    by 0x4F6E27D: call_ll_exitfuncs (pythonrun.c:2712)
==19187==    by 0x4F6E27D: Py_Finalize (pythonrun.c:746)
==19187==    by 0x4F860D8: Py_Main (main.c:771)
==19187==    by 0x108BE6: main (python.c:69)
==19187==  Address 0x6bd1c08 is 24 bytes inside an unallocated block of size 1,040 in arena "cli

This is line:


Looks like the LrErr_Exception is getting put into a bad state somehow.

I did this because I first saw a crash in python3 doing this:

Core was generated by `/usr/bin/python3 /usr/bin/ipython3'.
Program terminated with signal SIGABRT, Aborted.
#0  0x00007fb6a0744a98 in raise () from /lib64/libc.so.6
(gdb) bt
#0  0x00007fb6a0744a98 in raise () from /lib64/libc.so.6
#1  0x00007fb6a074669a in abort () from /lib64/libc.so.6
#2  0x00007fb6a0787e1a in __libc_message () from /lib64/libc.so.6
#3  0x00007fb6a078e1e4 in malloc_printerr () from /lib64/libc.so.6
#4  0x00007fb6a0790ccf in _int_free () from /lib64/libc.so.6
#5  0x00007fb6a0793bcc in free () from /lib64/libc.so.6
#6  0x00007fb68d350d0a in _PR_Fini () from /lib64/libnspr4.so
#7  0x00007fb6a1897d47 in _dl_fini () from /lib64/ld-linux-x86-64.so.2
#8  0x00007fb6a0749658 in __run_exit_handlers () from /lib64/libc.so.6
#9  0x00007fb6a07496a5 in exit () from /lib64/libc.so.6
#10 0x00007fb6a0730587 in __libc_start_main () from /lib64/libc.so.6
#11 0x00005579ac486c89 in _start ()

But now I cannot reproduce the crash.

Version-Release number of selected component (if applicable):
Comment 1 Fedora End Of Life 2016-11-24 07:40:41 EST
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '23'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 23 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 2 Fedora End Of Life 2016-12-20 09:50:43 EST
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

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