-
Notifications
You must be signed in to change notification settings - Fork 3
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
Run the jsc tests #23
Comments
With the latest builds of JSC we get a few test binaries. Here is the outcome of these:
|
Firstly - the important thing: I can reproduce this on my machine. It looks like (testapi): Before I do that, I intend to see whether we can build jscore-amigaos with a previous version of GCC (or without the call_once fix that we added). If we can, I would be interested to see if testapi works. EDIT: Guessing it was that test was just that though - a guess having had a quick look at the testapi source file. Actually, looks like the tests are all ran in threads, so not possible to predict. I am not so sure it is an actual test that is failing (could be still) versus the actual creation of threads for all of the the tests themselves. ===
Without a debugger to help, I can continue to look into this. |
I do not think it is anything to do with call_once. The issue seems to be in
Unfortunately I am dealing with the mess of new-age C++ template crazyness so it is hard to figure out even where the ProgramCounter goes after invoking this! What I do notice is that in SlotVisitor.cpp there are some macros involving a check as to whether we are MORPHOS/AMIGAOS. At the moment, my debugging is a matter of adding in printf()s, build, run on the X1000 next to my X5000. But, I think I have narrowed it down to task->run and something inside there. To be clear: I modified the testapi source code so that it is only running the test: |
What am I thinking. Of course, I have a debugger for the x86 machine. I can use the debugger on that machine to figure out where we jump to after the invocation of run(). I'll work on that when I come back from holiday. |
@3246251196 Thank you so much for all the work you do on figuring out what the problem is. |
Once cmake stage is passed, run the JSC tests. Those will expose many potential issues with threading / compiler suite
The text was updated successfully, but these errors were encountered: