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.

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

[sapphire] Error when calling bind on Windows #100

Closed
tysmith opened this issue Dec 14, 2019 · 1 comment
Closed

[sapphire] Error when calling bind on Windows #100

tysmith opened this issue Dec 14, 2019 · 1 comment
Assignees
Labels

Comments

@tysmith
Copy link
Collaborator

tysmith commented Dec 14, 2019

Traceback (most recent call last):
  File "grizzly\reduce\reduce.py", line 452, in run
    result = reducer.run()
  File "c:\users\user\code\fuzzmanager\lithium\src\lithium\reducer.py", line 1312, in run
    result = self.strategy.main(self.testcase, self.interesting, self.testcaseTempFilename)
  File "c:\users\user\code\fuzzmanager\lithium\src\lithium\reducer.py", line 378, in main
    result, anySingle, testcase = self.run(testcase, interesting, tempFilename)  # pylint: disable=invalid-name
  File "c:\users\user\code\fuzzmanager\lithium\src\lithium\reducer.py", line 454, in run
    if interesting(test_to_try):
  File "c:\users\user\code\fuzzmanager\lithium\src\lithium\reducer.py", line 1469, in interesting
    inter = self.conditionScript.interesting(self.conditionArgs, tempPrefix)
  File "grizzly\reduce\interesting.py", line 254, in interesting
    if self._run(testcase, run_prefix):
  File "grizzly\reduce\interesting.py", line 305, in _run
    self.server = sapphire.Sapphire()
  File "sapphire\core.py", line 221, in __init__
    self._socket = Sapphire._create_listening_socket(allow_remote, port)
  File "sapphire\core.py", line 270, in _create_listening_socket
    sock.bind(("0.0.0.0" if allow_remote else "127.0.0.1", port))
  File "C:\Python27\lib\socket.py", line 228, in meth
    return getattr(self._sock,name)(*args)
error: [Errno 10013] An attempt was made to access a socket in a way forbidden by its access permissions
@tysmith tysmith added the bug label Dec 14, 2019
@tysmith tysmith self-assigned this Mar 25, 2020
@tysmith
Copy link
Collaborator Author

tysmith commented Mar 25, 2020

Should be fixed by commit 60cfa22

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant