-
Notifications
You must be signed in to change notification settings - Fork 387
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Segmentation fault for concurrent > 1 #43
Comments
Would you mind testing this: http://download.joedog.org/siege/beta/siege-3.1.4-beta2.tar.gz (That version also includes an overhaul of cookie handling, namely stored Jeff On Sat, Dec 12, 2015 at 12:29 AM, Josh [email protected] wrote:
|
Actually worse if I try it with the version you requested. Now it seg faults with concurrent = 1. I went back and tried it again with 3.1.3 and it behaved as I specified, with concurrent = 1 it works, > 1 and it seg faults. |
I'm not sure what do. I don't have docker-alpine (honestly, I'm not even J. On Sun, Dec 13, 2015 at 1:57 AM, Josh [email protected] wrote:
|
No problem. Thanks for trying, for now I can use a debian docker image. It's much larger (170MB vs. 20MB), but it works. Docker alpine (https://github.com/gliderlabs/docker-alpine / http://alpinelinux.org/about/) is a minimal linux distro to make small Docker images. I might ask the Alpine guys if they've come across something similar. It's probably just a missing package. |
Let me know what you find out. J. On Tue, Dec 15, 2015 at 2:38 PM, Josh [email protected] wrote:
|
Here is the trace:
Valgrind:
|
This is related in part to my PR #42. Once I did get siege built in the docker-alpine base, when I ran siege with more than 1 concurrent users it would seg fault. I tried using gdb to get the backtrace (bt or where), but no trace was available. When I tried using the debian:jessie docker image as the base, I could use apt-get install siege (no build needed) and that worked just fine.
To recreate the segmentation fault:
The text was updated successfully, but these errors were encountered: