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
Created attachment 632576 [details] File: core_backtrace
Created attachment 632577 [details] File: environ
Created attachment 632578 [details] File: limits
Created attachment 632579 [details] File: backtrace
Created attachment 632580 [details] File: cgroup
Created attachment 632581 [details] File: smolt_data
Created attachment 632582 [details] File: maps
Created attachment 632583 [details] File: dso_list
Created attachment 632584 [details] File: proc_pid_status
Created attachment 632585 [details] File: var_log_messages
Created attachment 632586 [details] File: open_fds
Can you provide the cscope database you were using when this fault occured?
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.
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?
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
copy that. Please reopen if you can get it to reproduce.