-
Notifications
You must be signed in to change notification settings - Fork 7
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
Segfaults on OS X when calling Scraper.register(conn) #4
Comments
What has changed? What's different between then and now? I would expect any such problem to be deterministic. In other words, I would expect something important must have changed between when you had it working and now. |
From the stack-trace it looks like |
This is the thing that baffles me: I'm reasonably sure I'm running the exact same sequence of commands that I described in #2 and #3 but I'm now getting a different result. I don't think I've upgraded my system Python or anything like that. It's really weird. I notice that in #2 (comment) I installed the module and checked that it could be imported but did not attempt to use it. But I'm certain I saw the scraper example work with At least this time I've been able to get a stacktrace out of it. I wish I could answer your question about "what has changed" - because obviously something has, but I'm at a loss for what it is. |
Here's my current full steps-to-reproduce:
This dies with |
Huh... I appear to have fixed it! I used the above steps but I swapped out
The above example no longer segfaults. |
This is really weird. In #3 I reported that everything was working fine for me. Now I'm getting a setfault every time I try to run
register()
. Here's a sample session:The OS X crash reporter kicks in at this point, which means I can grab the following stack trace:
The text was updated successfully, but these errors were encountered: