-
Notifications
You must be signed in to change notification settings - Fork 387
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Siege 3.1.0 segfault when verbose is true #18
Comments
Lots of weirdness going on here. The line numbers don't seem to align with the core dump. For example, I'd expect #3 to correspond with notify.c:158 not 164. Personally, I'm unable to reproduce this problem. I've run multiple users in verbose mode across an array of consoles and it doesn't dump core. Do me a favor: move ~/.siegerc to something else, run siege.config to generate a new one, then try again. I wonder if something is mucking the formatting. |
By mistake i was set
which caused the issue. |
Yeah, but that's still a bug. You shouldn't be able to do anything which makes it dump core. I'll look at it. Thanks for bringing this to my attention. UPDATE: I tied display-id = ture and display_id = ture and I can't get it to dump core. Any chance you still have the .siegerc file that caused the issue? UPDATED UPDATE: I did indeed find a bug and fixed it. client.c has been updated in the main branch. |
Awesome, thanks ! |
I notice that siege (3.1.0) segfault's when you have configured concurrent users > 1 and verbose = true (both with compiled version and that one provide from repository).
If verbose is set to false, then no crash occurred even with concurrent users > 1.
Here is the backtrace:
The text was updated successfully, but these errors were encountered: