Project

General

Profile

Actions

Bug #1263

closed

Segmentation fault in mod_scgi

Added by jtate over 17 years ago. Updated almost 17 years ago.

Status:
Fixed
Priority:
Normal
Category:
core
Target version:
ASK QUESTIONS IN Forums:

Description

I believe this happens when an existing scgi request is in progress when the other side of the scgi socket closes the connection.

Here's the backtrace from gdb

(gdb) bt
#0  0xb7cb5d3b in strlen () from /lib/libc.so.6
#1  0x0805ba75 in buffer_append_string (b=0x806f308, s=0xd <Address 0xd out of bounds>) at buffer.c:171
#2  0x0805cf81 in log_error_write (srv=0x806f008, filename=0xd <Address 0xd out of bounds>, line=13,
    fmt=0xb7ef91c2 "sd") at log.c:192
#3  0xb7ef7a2d in scgi_handle_fdevent (s=0x806f008, ctx=0x80c1fe0, revents=25) at mod_scgi.c:2539
#4  0x0804e52e in main (argc=14, argv=0xbff62744) at server.c:1309

I'll attach the valgrind log.


Files

lighttpd.14669 (22.2 KB) lighttpd.14669 valgrind log jtate, 2007-07-16 19:30
murder-lighttpd.py (1.55 KB) murder-lighttpd.py Python SCGI server that kills lighttpd jtate, 2007-07-17 17:10
lighttpd.conf.test (1.47 KB) lighttpd.conf.test test configuration jtate, 2007-07-17 17:10
#4

Updated by jan over 17 years ago

  • Status changed from New to Fixed
  • Resolution set to fixed
Actions

Also available in: Atom