Bug 2256515 - [abrt] cscope: freefilelist(): cscope killed by SIGABRT
Summary: [abrt] cscope: freefilelist(): cscope killed by SIGABRT
Keywords:
Status: CLOSED DUPLICATE of bug 2269887
Alias: None
Product: Fedora
Classification: Fedora
Component: cscope
Version: 39
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Vladis Dronov (Fedora)
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:f264275202cc1cf094538ba326d...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-01-02 20:50 UTC by Jeff Frontz
Modified: 2024-07-31 16:31 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2024-07-30 21:13:55 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: mountinfo (2.99 KB, text/plain)
2024-01-02 20:50 UTC, Jeff Frontz 		no flags Details
File: environ (3.51 KB, text/plain)
2024-01-02 20:51 UTC, Jeff Frontz 		no flags Details
File: core_backtrace (4.85 KB, text/plain)
2024-01-02 20:51 UTC, Jeff Frontz 		no flags Details
File: backtrace (20.21 KB, text/plain)
2024-01-02 20:51 UTC, Jeff Frontz 		no flags Details
File: limits (1.29 KB, text/plain)
2024-01-02 20:51 UTC, Jeff Frontz 		no flags Details
File: proc_pid_status (1.43 KB, text/plain)
2024-01-02 20:51 UTC, Jeff Frontz 		no flags Details
File: cpuinfo (3.08 KB, text/plain)
2024-01-02 20:51 UTC, Jeff Frontz 		no flags Details
File: os_info (734 bytes, text/plain)
2024-01-02 20:51 UTC, Jeff Frontz 		no flags Details
File: dso_list (423 bytes, text/plain)
2024-01-02 20:51 UTC, Jeff Frontz 		no flags Details
File: maps (3.03 KB, text/plain)
2024-01-02 20:51 UTC, Jeff Frontz 		no flags Details
File: open_fds (439 bytes, text/plain)
2024-01-02 20:51 UTC, Jeff Frontz 		no flags Details
View All

Description Jeff Frontz 2024-01-02 20:50:55 UTC 
Version-Release number of selected component:
cscope-15.9-19.fc39

Additional info:
reporter:       libreport-2.17.11
type:           CCpp
cmdline:        cscope -q
crash_function: freefilelist
journald_cursor: s=e4088658a0714877804d96009e957f5e;i=3451e;b=cafa2f0ddd9d4d5299aa89c4a0fd840b;m=20d3611e712;t=60cbdee5a88e1;x=156832068a4e2923
executable:     /usr/bin/cscope
rootdir:        /
uid:            1000
kernel:         6.5.11-300.fc39.x86_64
package:        cscope-15.9-19.fc39
runlevel:       N 5
cgroup:         0::/user.slice/user-1000.slice/session-60.scope
reason:         cscope killed by SIGABRT
backtrace_rating: 4

Truncated backtrace:
Thread no. 1 (2 frames)
 #13 freefilelist at /usr/src/debug/cscope-15.9-19.fc39.x86_64/src/dir.c:727
 #14 myexit at /usr/src/debug/cscope-15.9-19.fc39.x86_64/src/main.c:1079
Comment 1 Jeff Frontz 2024-01-02 20:50:59 UTC 
Created attachment 2006890 [details]
File: mountinfo
Comment 2 Jeff Frontz 2024-01-02 20:51:00 UTC 
Created attachment 2006891 [details]
File: environ
Comment 3 Jeff Frontz 2024-01-02 20:51:01 UTC 
Created attachment 2006892 [details]
File: core_backtrace
Comment 4 Jeff Frontz 2024-01-02 20:51:03 UTC 
Created attachment 2006893 [details]
File: backtrace
Comment 5 Jeff Frontz 2024-01-02 20:51:05 UTC 
Created attachment 2006894 [details]
File: limits
Comment 6 Jeff Frontz 2024-01-02 20:51:08 UTC 
Created attachment 2006895 [details]
File: proc_pid_status
Comment 7 Jeff Frontz 2024-01-02 20:51:09 UTC 
Created attachment 2006896 [details]
File: cpuinfo
Comment 8 Jeff Frontz 2024-01-02 20:51:11 UTC 
Created attachment 2006897 [details]
File: os_info
Comment 9 Jeff Frontz 2024-01-02 20:51:13 UTC 
Created attachment 2006898 [details]
File: dso_list
Comment 10 Jeff Frontz 2024-01-02 20:51:14 UTC 
Created attachment 2006899 [details]
File: maps
Comment 11 Jeff Frontz 2024-01-02 20:51:16 UTC 
Created attachment 2006900 [details]
File: open_fds
Comment 12 Vladis Dronov 2024-07-30 21:13:55 UTC 
it looks like cscope was killed by SIGABRT, presumably, at container exit. cscope itself looks ok.

> abort() is usually called by library functions which detect an internal error or some seriously
> broken constraint. For example malloc() will call abort() if its internal structures are damaged
> by a heap overflow.
Comment 13 Jeff Frontz 2024-07-31 16:31:01 UTC 
> container exit

I'm not sure what you mean by "container", but just in case: this was being run via an interactive shell on the base OS (no docker, etc. involved).

*** This bug has been marked as a duplicate of bug 2269887 ***
Note You need to log in before you can comment on or make changes to this bug.