Bug 869530

Summary: [abrt] cscope-15.8-3.fc18: myexit: Process /usr/bin/cscope was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Qingtang Zhou <qzhou>
Component: cscopeAssignee: Neil Horman <nhorman>
Status: CLOSED WORKSFORME QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: michen, nhorman
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:67a5c0b88e8f8a3d7933bd3c4cd1c3d7ef580b5a
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-10-29 12:55:47 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: core_backtrace
none
File: environ
none
File: limits
none
File: backtrace
none
File: cgroup
none
File: smolt_data
none
File: maps
none
File: dso_list
none
File: proc_pid_status
none
File: var_log_messages
none
File: open_fds
none
cscope database none

Description Qingtang Zhou 2012-10-24 07:50:12 UTC 
Description of problem:
Query a string in vim which has a cscope database link.

Version-Release number of selected component:
cscope-15.8-3.fc18

Additional info:
libreport version: 2.0.16
abrt_version:   2.0.16
backtrace_rating: 4
cmdline:        /usr/bin/cscope -dl -f /home/qzhou/private/libvirt/src/cscope.out
crash_function: myexit
kernel:         3.7.0-0.rc1.git1.1.fc19.x86_64

truncated backtrace:
:Thread no. 1 (8 frames)
: #2 myexit at main.c:1060
: #4 __read_nocancel at ../sysdeps/unix/syscall-template.S:81
: #5 _IO_new_file_underflow at fileops.c:613
: #6 _IO_default_uflow at genops.c:436
: #7 _IO_getline_info at iogetline.c:69
: #8 _IO_getline at iogetline.c:38
: #9 _IO_fgets at iofgets.c:56
: #10 fgets at /usr/include/bits/stdio2.h:263
Comment 1 Qingtang Zhou 2012-10-24 07:50:16 UTC 
Created attachment 632576 [details]
File: core_backtrace
Comment 2 Qingtang Zhou 2012-10-24 07:50:19 UTC 
Created attachment 632577 [details]
File: environ
Comment 3 Qingtang Zhou 2012-10-24 07:50:23 UTC 
Created attachment 632578 [details]
File: limits
Comment 4 Qingtang Zhou 2012-10-24 07:50:27 UTC 
Created attachment 632579 [details]
File: backtrace
Comment 5 Qingtang Zhou 2012-10-24 07:50:31 UTC 
Created attachment 632580 [details]
File: cgroup
Comment 6 Qingtang Zhou 2012-10-24 07:50:34 UTC 
Created attachment 632581 [details]
File: smolt_data
Comment 7 Qingtang Zhou 2012-10-24 07:50:38 UTC 
Created attachment 632582 [details]
File: maps
Comment 8 Qingtang Zhou 2012-10-24 07:50:42 UTC 
Created attachment 632583 [details]
File: dso_list
Comment 9 Qingtang Zhou 2012-10-24 07:50:45 UTC 
Created attachment 632584 [details]
File: proc_pid_status
Comment 10 Qingtang Zhou 2012-10-24 07:50:48 UTC 
Created attachment 632585 [details]
File: var_log_messages
Comment 11 Qingtang Zhou 2012-10-24 07:50:53 UTC 
Created attachment 632586 [details]
File: open_fds
Comment 12 Neil Horman 2012-10-24 13:26:45 UTC 
Can you provide the cscope database you were using when this fault occured?
Comment 13 Qingtang Zhou 2012-10-25 15:51:52 UTC 
Created attachment 633434 [details]
cscope database

Hi, Neil,
Sorry for a delay, The attachment is the cscope database.
I generated it from libvirt's source code, with cmd:
# cd /path/to/libvirt/src
# find `pwd` -name "*.[ch]" > cscope.files
# cscope -bqRv

Then add this database in vim:
":cs add cscope.out"

When I query some symbol, abrt told me cscope crash.
Comment 14 Neil Horman 2012-10-25 19:19:53 UTC 
Interesting, this doesn't fail on my F17 system, either using your cscope database or by generating my own locally here.  Is this system internal to redhat where the problem is occuring? Is it possible for me to have access to it?
Comment 15 Qingtang Zhou 2012-10-29 05:51:08 UTC 
Hi, Neil,

The box is my working pc... 

I tried to reproduce this problem on a testing machine these days, but I failed. so I guess you can close this bz first, I'll re-open it when I meet this problem again. :p
Comment 16 Neil Horman 2012-10-29 12:55:47 UTC 
copy that.  Please reopen if you can get it to reproduce.