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

"This should probably never happen???" #22

Closed
kaeluka opened this issue Aug 3, 2014 · 4 comments
Closed

"This should probably never happen???" #22

kaeluka opened this issue Aug 3, 2014 · 4 comments
Assignees

Comments

@kaeluka
Copy link
Contributor

kaeluka commented Aug 3, 2014

In file tit_lazy.c, there's a debug print statement that prints "RUNNING!\n": https://github.com/parapluu/mylittlepony/blob/0c89f84f0aba1fadc7b6ae43ff136acd956cc3ce/src/runtime/future/tit_lazy.c#L159-L161
Above, a comment says that "This should probably never happen???". I just saw it happen, programs/ex_active.enc triggers it sometimes:

../programs $ ./ex_active.enc
./ex_active.pony.c:203:13: warning: unused variable '_tmp19' [-Wunused-variable]
  future_t* _tmp19 = _tmp17;;
            ^
1 warning generated.
waiting for result...
obj2
obj2
obj2
obj2
obj2
obj1
obj1
obj1
obj1
obj1
RUNNING!
got result
obj1
@EliasC
Copy link
Contributor

EliasC commented Aug 8, 2014

@TobiasWrigstad Just a reminder for you to look into this. I see it happen from time to time as well.

@TobiasWrigstad
Copy link
Contributor

Thanks. It is on my list but not urgent since it seems not to cause crashes. If you are annoyed by the printout, please remove it since this ticket will remember the need to look at it.

@EliasC
Copy link
Contributor

EliasC commented Dec 9, 2014

Let's remember to check if this thing stops happening when the new futures arrive!

@TobiasWrigstad
Copy link
Contributor

I am sure it will be since the lightweight threads implementation is redone as part of it.

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

No branches or pull requests

3 participants