On Thu, Aug 04, 2005 at 11:48:04PM -0700, Jeff Breidenbach wrote: [...] > apt-get source siege > cd siege-2.61 > ./configure > make > gdb ./siege > [...] > > (gdb) run http://localhost > Starting program: /tmp/siege-2.61/src/siege http://localhost > [Thread debugging using libthread_db enabled] > [New Thread 46912500748432 (LWP 25666)] > ** siege 2.61 > ** Preparing 0 concurrent users for battle. > The server is now under siege...[New Thread 1082460528 (LWP 25684)] > > Program received signal SIGSEGV, Segmentation fault.
I know this was a long time ago, but... could you, please, confirm if this bug still happens? I'v tried to reproduce it on 2.6.8-9-amd64-k8 (AMD Athlon(tm) 64) and 2.6.10-em64t-smp (Intel(R) Xeon(TM)) exactly as written above by you and I had no problems on both of this machines. TIA Richard. -- "First they ignore you. Then they laugh at you. Then they fight you. Then you win." - Mohandas Gandhi. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
