apache:troubleshooting:determine_why_an_apache_process_hung
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | |||
apache:troubleshooting:determine_why_an_apache_process_hung [2021/02/02 11:05] – [Use gcore utility to force a hung process to dump its core] peter | apache:troubleshooting:determine_why_an_apache_process_hung [2021/02/02 11:05] (current) – [Use gdb utility to retrieve a stack backtrace from the core file] peter | ||
---|---|---|---|
Line 127: | Line 127: | ||
**NOTE: | **NOTE: | ||
- | | + | * **accept ()**: Apache was in the **accept()** system call when the SIGSEGV signal |
- | + | ||
- | | + | |
* **accept()** was called by the portable runtime method **apr_socket_accept()**. | * **accept()** was called by the portable runtime method **apr_socket_accept()**. | ||
</ | </ |
apache/troubleshooting/determine_why_an_apache_process_hung.1612263919.txt.gz · Last modified: 2021/02/02 11:05 by peter