Skip to content

Segmentation fault for concurrent > 1 #43

@joshuamorris3

Description

@joshuamorris3

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:

  1. docker run --rm -it alpine sh
  2. Add the build dependencies: apk add --update alpine-sdk
  3. wget http://download.joedog.org/siege/siege-latest.tar.gz
  4. tar -zxvf siege-latest.tar.gz
  5. cd siege-3.1.3
  6. ./configure
  7. Add #include <sys/types.h> below line 24 of src/hash.c
  8. make
  9. Run the following: siege -r 1 -c 2 www.google.com

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions