Bug 1226712 - [abrt] httpd: httpd killed by SIGSEGV
Summary: [abrt] httpd: httpd killed by SIGSEGV
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: httpd
Version: 20
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jan Kaluža
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:2f7d82aa21b5d1cf528783696b1...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-05-31 20:54 UTC by Stefan Loones
Modified: 2015-06-30 00:27 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-06-30 00:27:42 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (13.89 KB, text/plain)
2015-05-31 20:54 UTC, Stefan Loones
no flags Details
File: cgroup (164 bytes, text/plain)
2015-05-31 20:54 UTC, Stefan Loones
no flags Details
File: core_backtrace (258 bytes, text/plain)
2015-05-31 20:54 UTC, Stefan Loones
no flags Details
File: dso_list (10.68 KB, text/plain)
2015-05-31 20:54 UTC, Stefan Loones
no flags Details
File: environ (110 bytes, text/plain)
2015-05-31 20:54 UTC, Stefan Loones
no flags Details
File: limits (1.29 KB, text/plain)
2015-05-31 20:54 UTC, Stefan Loones
no flags Details
File: maps (51.99 KB, text/plain)
2015-05-31 20:54 UTC, Stefan Loones
no flags Details
File: open_fds (156 bytes, text/plain)
2015-05-31 20:54 UTC, Stefan Loones
no flags Details
File: proc_pid_status (913 bytes, text/plain)
2015-05-31 20:54 UTC, Stefan Loones
no flags Details

Description Stefan Loones 2015-05-31 20:54:22 UTC
Description of problem:
Experimenting with the sample module Autogenerated via "apxs -n modulename -g''

Version-Release number of selected component:
httpd-2.4.10-2.fc20

Additional info:
reporter:       libreport-2.2.3
backtrace_rating: 3
cmdline:        /usr/sbin/httpd -DFOREGROUND
executable:     /usr/sbin/httpd
kernel:         3.19.5-100.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            0
var_log_messages: [System Logs]:\n-- Logs begin at Mon 2014-12-29 20:25:20 CET, end at Sun 2015-05-31 22:41:39 CEST. --

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 ??
 #1 _dl_close_worker at dl-close.c:272
 #2 _dl_close at dl-close.c:782
 #3 _dl_catch_error at dl-error.c:177
 #4 _dlerror_run at dlerror.c:163
 #5 __dlclose at dlclose.c:46
 #6 dso_cleanup at dso/unix/dso.c:72
 #7 run_cleanups at memory/unix/apr_pools.c:2352
 #8 apr_pool_destroy at memory/unix/apr_pools.c:814
 #10 destroy_and_exit_process at main.c:264

Comment 1 Stefan Loones 2015-05-31 20:54:26 UTC
Created attachment 1032970 [details]
File: backtrace

Comment 2 Stefan Loones 2015-05-31 20:54:27 UTC
Created attachment 1032971 [details]
File: cgroup

Comment 3 Stefan Loones 2015-05-31 20:54:28 UTC
Created attachment 1032972 [details]
File: core_backtrace

Comment 4 Stefan Loones 2015-05-31 20:54:30 UTC
Created attachment 1032973 [details]
File: dso_list

Comment 5 Stefan Loones 2015-05-31 20:54:31 UTC
Created attachment 1032974 [details]
File: environ

Comment 6 Stefan Loones 2015-05-31 20:54:32 UTC
Created attachment 1032975 [details]
File: limits

Comment 7 Stefan Loones 2015-05-31 20:54:34 UTC
Created attachment 1032976 [details]
File: maps

Comment 8 Stefan Loones 2015-05-31 20:54:35 UTC
Created attachment 1032977 [details]
File: open_fds

Comment 9 Stefan Loones 2015-05-31 20:54:36 UTC
Created attachment 1032978 [details]
File: proc_pid_status

Comment 10 Fedora End Of Life 2015-06-30 00:27:42 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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
bug.

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.