Bug 755171 - [abrt] yum-3.4.3-5.fc16: pthread_join: Process /usr/bin/python was killed by signal 6 (SIGABRT)
Summary: [abrt] yum-3.4.3-5.fc16: pthread_join: Process /usr/bin/python was killed by ...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: curl
Version: 16
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kamil Dudka
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:661a75cf1c3150c30080534a29e...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-19 10:10 UTC by Bruno Martins
Modified: 2014-01-21 23:20 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-01-11 12:33:07 UTC
Type: ---

Attachments (Terms of Use)
File: environ (2.75 KB, text/plain)
2011-11-19 10:10 UTC, Bruno Martins 		no flags Details
File: dso_list (9.27 KB, text/plain)
2011-11-19 10:10 UTC, Bruno Martins 		no flags Details
File: build_ids (4.04 KB, text/plain)
2011-11-19 10:10 UTC, Bruno Martins 		no flags Details
File: smolt_data (2.93 KB, text/plain)
2011-11-19 10:10 UTC, Bruno Martins 		no flags Details
File: var_log_messages (3.71 KB, text/plain)
2011-11-19 10:10 UTC, Bruno Martins 		no flags Details
File: backtrace (115.49 KB, text/plain)
2011-11-19 10:10 UTC, Bruno Martins 		no flags Details
File: maps (36.32 KB, text/plain)
2011-11-19 10:10 UTC, Bruno Martins 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Bruno Martins 2011-11-19 10:10:24 UTC 
libreport version: 2.0.7
abrt_version:   2.0.6
backtrace_rating: 4
cmdline:        /usr/bin/python /usr/bin/yum search browser
comment:        Did 'yum search browser'.
crash_function: pthread_join
executable:     /usr/bin/python
kernel:         3.1.1-2.fc16.x86_64
pid:            4861
pwd:            /home/skorzen
reason:         Process /usr/bin/python was killed by signal 6 (SIGABRT)
time:           Fri 18 Nov 2011 07:40:01 PM WET
uid:            1000
username:       skorzen

backtrace:      Text file, 118257 bytes
build_ids:      Text file, 4141 bytes
dso_list:       Text file, 9489 bytes
environ:        Text file, 2814 bytes
maps:           Text file, 37193 bytes
smolt_data:     Text file, 2996 bytes
var_log_messages: Text file, 3796 bytes
Comment 1 Bruno Martins 2011-11-19 10:10:28 UTC 
Created attachment 534550 [details]
File: environ
Comment 2 Bruno Martins 2011-11-19 10:10:31 UTC 
Created attachment 534551 [details]
File: dso_list
Comment 3 Bruno Martins 2011-11-19 10:10:33 UTC 
Created attachment 534552 [details]
File: build_ids
Comment 4 Bruno Martins 2011-11-19 10:10:35 UTC 
Created attachment 534553 [details]
File: smolt_data
Comment 5 Bruno Martins 2011-11-19 10:10:37 UTC 
Created attachment 534554 [details]
File: var_log_messages
Comment 6 Bruno Martins 2011-11-19 10:10:40 UTC 
Created attachment 534555 [details]
File: backtrace
Comment 7 Bruno Martins 2011-11-19 10:10:43 UTC 
Created attachment 534556 [details]
File: maps
Comment 8 Zdeněk Pavlas 2011-11-21 08:38:34 UTC 
Invalid free() in getaddrinfo()?  glibc bug?
Comment 9 Kamil Dudka 2011-11-21 13:20:22 UTC 
I cannot see anything wrong in libcurl.  Is this crash something easy to reproduce?

I tried 'yum search browser' on a Fedora 16 with glibc-2.14.90-16 and it worked just fine.  Even the output of valgrind was sane (modulo some false positives on gcc-generated string routines).
Comment 10 Zdeněk Pavlas 2011-11-21 14:45:27 UTC 
I can't reproduce it either.  Traceback shows the bug triggered from pycurl's resolver but something else might have corrupted the heap already (libc, python, rpm C modules).
Comment 11 Kamil Dudka 2012-01-11 12:33:07 UTC 
We have not enough information to reproduce the problem.  Feel free to reopen if your have a reliable reproducer.
Note You need to log in before you can comment on or make changes to this bug.