siege crashed with SIGSEGV in start_thread()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
siege (Ubuntu) |
Invalid
|
Medium
|
Unassigned |
Bug Description
Binary package hint: siege
Before the crash, stderr shows this kind of errors:
Error: socket: 1157667152 connection refused.: Connection refused
Error: unable to shutdown the socket: Transport endpoint is not connected
ProblemType: Crash
Architecture: amd64
Date: Wed Sep 26 18:21:08 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/siege
NonfreeKernelMo
Package: siege 2.65-4build1
PackageArchitec
ProcCmdline: siege -i -f filtered.urls -H Cookie:\ sessionid=
ProcCwd: /home/g2p/
ProcEnviron:
SHELL=/bin/bash
PATH=/
LANG=fr_FR.UTF-8
Signal: 11
SourcePackage: siege
StacktraceTop:
?? ()
?? ()
?? ()
?? ()
start_thread () from /lib/libpthread
Title: siege crashed with SIGSEGV in start_thread()
Uname: Linux g2p-desktop 2.6.22-12-generic #1 SMP Thu Sep 20 18:19:18 GMT 2007 x86_64 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin netdev plugdev powerdev scanner video
SegvAnalysis:
Segfault happened at: 0x4076e5 <fflush@plt+17589>: movb $0x0,(%rbx)
PC (0x004076e5) ok
source "$0x0" ok
destination "(%rbx)" (0x00000000) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
StacktraceTop: http_request (C=0x93f050, U=0x75df80, client=0x639ac0) at client.c:294 .so.0
start_routine (client=0x639ac0) at client.c:146
crew_thread (crew=<value optimized out>) at crew.c:134
start_thread () from /lib/libpthread
clone () from /lib/libc.so.6