siege crashed with SIGSEGV in start_thread()

[Gabriel de Perthuis]

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
NonfreeKernelModules: cdrom
Package: siege 2.65-4build1
PackageArchitecture: amd64
ProcCmdline: siege -i -f filtered.urls -H Cookie:\ sessionid=a6675e9618c94b9072822e4dcb7ebf4d
ProcCwd: /home/g2p/work/paperblog
ProcEnviron:
 SHELL=/bin/bash
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=fr_FR.UTF-8
Signal: 11
SourcePackage: siege
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 start_thread () from /lib/libpthread.so.0
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

[Apport retracing service (apport)]

StacktraceTop:http_request (C=0x93f050, U=0x75df80, client=0x639ac0) at client.c:294
start_routine (client=0x639ac0) at client.c:146
crew_thread (crew=<value optimized out>) at crew.c:134
start_thread () from /lib/libpthread.so.0
clone () from /lib/libc.so.6

[Connor Imes (ckimes)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Gutsy is no longer supported. Thanks in advance.

[Chuck Short (zulcss)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!