Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Random crash #1

Open
cstanfill opened this issue Apr 30, 2011 · 3 comments
Open

Random crash #1

cstanfill opened this issue Apr 30, 2011 · 3 comments

Comments

@cstanfill
Copy link
Member

The server program occasionally segfaults for no apparent reason. Happens when it is being hammered - running the stresser script with 127.0.0.1 6667 100000 will generally cause it within 10-20 connections. Haven't investigated much.
@frozencemetery
Copy link

If this is a threading issue, perhaps setting the new connections to a clock heartbeat of some kind would help?

@cstanfill
Copy link
Member Author

Hm. Will look into it. Bug now also manifests itself in the form of the program suddenly exiting without a segfault.

@cstanfill cstanfill reopened this May 8, 2011
@cstanfill
Copy link
Member Author

The non-segfault version has been resolved; it was exiting on SIGPIPE; a flag passed to the send command fixes that. Need to catch the error it does return, though. Not sure how to reproduce the segfault now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@frozencemetery @cstanfill