On 11/23/2012 04:55 AM, Josue Abarca wrote: > On Wed, Nov 21, 2012 at 04:56:55PM +0200, Török Edwin wrote: >> Package: siege >> Version: 2.70-4 >> Severity: normal > ... >> Architecture: amd64 >> Kernel: Linux 3.6.6 >> >> Debian Release: wheezy/sid >> 500 unstable ftp.ro.debian.org >> 1 experimental ftp.ro.debian.org >> >> --- Package information. --- >> Depends (Version) | Installed >> ==========================-+-=========== >> libc6 (>= 2.7) | >> libssl1.0.0 (>= 1.0.0) | > > Which versions of libc6 and libssl1.0.0 are you using? > > I am trying to reproduce with the latest versions in sid: > $ dpkg -l libc6 > ii libc6:amd64 2.13-37 amd64 > > $ dpkg -l libssl1.0.0 > ii libssl1.0.0:am 1.0.1c-4 amd64
I've got the same. > > I have been trying, but I have not been able to reproduce the bug. > > Maybe you could try to reproduce it with upstream "2.70" version > http://www.joedog.org/pub/siege/siege-2.70.tar.gz It doesn't crash, and valgrind doesn't say anything either. I've done an 'apt-get source siege', and that doesn't crash either if I manually build it (using a simple ./configure && make). Maybe it has something to do with the way the Debian package is built (I see its using hardening-wrapper). I've rebuilt the Debian package using pbuilder in a wheezy chroot and a squeeze chroot. None of them crash. I've just checked again and /usr/bin/siege from the Debian repository still crashes. > > In the mean time I'll prepare a debug symbols package for you. Do you remember what environment/compiler versions where used to build it? Because apparently simply rebuilding the package makes the crash go away, which makes me believe that it might be due to a compiler bug? > > Here is my output, using your ".siegerc" file: > > $ siege -R .siegerc http://www.jmaslibre.org/index.html > ** SIEGE 2.70 > ** Preparing 15 concurrent users for battle. > The server is now under siege... > Lifting the server siege... done. > Transactions: 11 hits > Availability: 100.00 % > Elapsed time: 9.32 secs > Data transferred: 0.00 MB > Response time: 2.21 secs > Transaction rate: 1.18 trans/sec > Throughput: 0.00 MB/sec > Concurrency: 2.61 > Successful transactions: 11 > Failed transactions: 0 > Longest transaction: 5.37 > Shortest transaction: 5.33 > > FILE: /var/tmp/siege.log > You can disable this annoying message by editing > the .siegerc file in your home directory; change > the directive 'show-logfile' to false. > > $ siege -R .siegerc http://debian.home.lan/index.html > ** SIEGE 2.70 > ** Preparing 15 concurrent users for battle. > The server is now under siege... > Lifting the server siege... done. > Transactions: 269 hits > Availability: 100.00 % > Elapsed time: 9.95 secs > Data transferred: 0.04 MB > Response time: 0.00 secs > Transaction rate: 27.04 trans/sec > Throughput: 0.00 MB/sec > Concurrency: 0.11 > Successful transactions: 269 > Failed transactions: 0 > Longest transaction: 0.02 > Shortest transaction: 0.00 > > FILE: /var/tmp/siege.log > You can disable this annoying message by editing > the .siegerc file in your home directory; change > the directive 'show-logfile' to false. > > > Cheers, > -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
