siege package (in testing repo) seg faults
Siege appears to segfault very often, usually after sending a handful of requests. It appears to be more reliable in quiet mode (-q flag) and I’ve not got it to seg fault with a single request yet (e.g. "siege -g www.google.com).
At least one one problem is the following (thanks to ^7heo):
_*stack_chk_fail () at src/env/*_stack_chk_fail.c:18
Tests were performed with the default configuration file (run “siege.config” to generate it).
(from redmine: issue id 3501, created on 2014-11-06, closed on 2019-06-11)
- Changesets:
- Revision 0079449e by Natanael Copa on 2014-11-12T13:14:58Z:
testing/siege: enable -dbg
ref #3501
- Uploads:
- valgrind_siege_output.txt siege through valgrind, output of
- valgrind_siege3.0.8.out.txt