Actions
Bug #496
closedlighttpd crashes when receiving SIGPIPE
Status:
Invalid
Priority:
High
Category:
core
Target version:
-
ASK QUESTIONS IN Forums:
Description
lighttpd crashes with SIGPIPE on Debian Linux on a AMD64 Dual Opteron machine using lighttpd 1.4.9 from source compiled
# gdb ./sbin/lighttpd
GNU gdb 6.3-debian
[..]
This GDB was configured as "x86_64-linux"...Using host libthread_db library "/lib/libthread_db.so.1".
(gdb) run -D -f light.conf
Starting program: /usr/local/lighttpd/sbin/lighttpd -D -f light.conf
Program received signal SIGPIPE, Broken pipe.
0x0000002a9594b2e8 in writev () from /lib/libc.so.6
(gdb) bt
#0 0x0000002a9594b2e8 in writev () from /lib/libc.so.6
#1 0x000000000041a8c1 in network_write_chunkqueue_linuxsendfile (srv=0x527010,
con=0x96ad90, fd=563, cq=0x96b310) at network_linux_sendfile.c:79
#2 0x000000000040bafd in network_write_chunkqueue (srv=0x527010, con=0x96ad90,
cq=0x96b310) at network.c:614
#3 0x000000000040929d in connection_handle_write (srv=0x527010, con=0x96ad90)
at connections.c:528
#4 0x000000000040ab5c in connection_state_machine (srv=0x527010, con=0x96ad90)
at connections.c:1585
#5 0x0000000000406e66 in main (argc=51, argv=0x1) at server.c:1164
(gdb) quit
Updated by jan about 19 years ago
- Status changed from New to Fixed
- Resolution set to invalid
This is not a crash. It is the default behaviour of SIGPIPE.
In lighttpd we ignore the signal and handle the corresponding return-codes in writev() ourself.
In GDB the SIGPIPE will be raised whenever a connection is closed while writing. Just type 'cont' to go on.
Actions
Also available in: Atom