-
Notifications
You must be signed in to change notification settings - Fork 68
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
Forward reference to thread variable segfaults #590
Comments
The variable/constant needn't be a thread variable. I just ran into the same problem with protocol buffers, in which I tried to update an Since we do library-at-a-time compilation, I assume that we have a view of all the definitions regardless of file. We may or may not currently be able to infer a complete ordering? It would be great if we could emit a serious warning for such code ("attempt to use |
I'm dropping this here on the theory that it's a similar/related issue. I have top-level code that makes an instance of
|
Open Dylan 2013.1
OS X
In testworks I was rearranging the code into different files and started getting a segfault during library initialization. It was fairly hard to debug. Turned out to be a forward reference to a thread variable in a different file. i.e., the file occurred later in the LID file. Here's a library that reproduces the problem:
The text was updated successfully, but these errors were encountered: