pthreadhint
87102262 [logout]
matrix multiplication
phase 1 of 3:
submit your code
Submit your matrix multiplication code below. You can upload C/C++ codes:
Last Submission: April 12, 2014, 5:32 p.m. [preview]

phase 2 of 3:
run your code
Here you can run your latest submission.
Be warned:
  • You can only run your code every 10 minutes.
  • If your code tries anything malicious, it will get killed*.
When you are ready, push the button.
*
anyway your code will run in a sandboxed environment, in the middle of a desert. alone and helpless.

phase 3 of 3:
code analysis
(simple)
Simple (1 of 3)
In this test case two matrices are multiplied.
8234
9357
23
45
67
93
=
7867
12398
You should only create two threads for row multiplication.
Raw Input
2
2x4
8 2 3 4
9 3 5 7
4x2
2 3
4 5
6 7
9 3
Overall Result
Compilation
Compilation succeeded.
Successful
Maliciousness
Your code was considered safe. Keep it this way.
Safe
Thread Problems
Errors found with your threads. In case of errors, you can see more info in thread error analysis section.
2
Memory Problems
Number of problems with your memory usage. In case of errors, you can see more info in memory analysis section.
7
Memory Analysis
In this section your memory usage is analyzed. Use it to find out if your code leaks and/or has illegal accesses to memory.
Invalid Use of Memory
You tried to write to an invalid address on line 104 of your code.
Yes
Invalid Use of Memory
You tried to write to an invalid address on line 51 of your code.
Yes
Illegal Free
You tried to free an invalid block of memory on line 51 of your code. You may have freed this block before.
Yes
Illegal Free
You tried to free an invalid block of memory on line 123 of your code. You may have freed this block before.
Yes
Leaked Bytes
Your code has leaked 16 bytes of memory. This means you have lost access to some blocks of memory before ending your program. Make sure you have freed all the memory you have allocated in your program.
16
Thread Error Analysis
Your program is analyzed for any kind of thread errors in this section. These errors are hard to find by manual debugging. For data race errors, you may see duplicate rows, as they are listed each time they happen.
Possible Data Race
There is a possiblity of data race in your code. You are using a block of memory on line 136 of your code, which conflicts with another thread's use of that block on line 130
Yes
Possible Data Race
There is a possiblity of data race in your code. You are using a block of memory on line 136 of your code, which conflicts with another thread's use of that block on line 130
Yes
Threads Execution Timeline
Here you can see the threads you have created along the time, and the locks they waited on, if any.
phase 3 of 3:
code analysis
(moderate)
Moderate (2 of 3)
In this test case four matrices are multiplied.
11
11
11
11
11
11
11
11
=
88
88
Raw Input
4
2x2
1 1
1 1
2x2
1 1
1 1
2x2
1 1
1 1
2x2
1 1
1 1
Overall Result
Compilation
Compilation succeeded.
Successful
Maliciousness
Your code was considered safe. Keep it this way.
Safe
Thread Problems
Errors found with your threads. In case of errors, you can see more info in thread error analysis section.
6
Memory Problems
Number of problems with your memory usage. In case of errors, you can see more info in memory analysis section.
42
Memory Analysis
In this section your memory usage is analyzed. Use it to find out if your code leaks and/or has illegal accesses to memory.
Invalid Use of Memory
You tried to write to an invalid address on line 51 of your code.
Yes
Illegal Free
You tried to free an invalid block of memory on line 51 of your code. You may have freed this block before.
Yes
Illegal Free
You tried to free an invalid block of memory on line 123 of your code. You may have freed this block before.
Yes
Invalid Use of Memory
You tried to write to an invalid address on line 102 of your code.
Yes
Invalid Use of Memory
You tried to write to an invalid address on line 103 of your code.
Yes
Invalid Use of Memory
You tried to write to an invalid address on line 55 of your code.
Yes
Invalid Use of Memory
You tried to write to an invalid address on line 55 of your code.
Yes
Invalid Use of Memory
You tried to write to an invalid address on line 104 of your code.
Yes
Invalid Use of Memory
You tried to write to an invalid address on line 55 of your code.
Yes
Invalid Use of Memory
You tried to write to an invalid address on line 55 of your code.
Yes
Invalid Use of Memory
You tried to write to an invalid address on line 104 of your code.
Yes
Invalid Use of Memory
You tried to write to an invalid address on line 51 of your code.
Yes
Illegal Free
You tried to free an invalid block of memory on line 51 of your code. You may have freed this block before.
Yes
Illegal Free
You tried to free an invalid block of memory on line 123 of your code. You may have freed this block before.
Yes
Leaked Bytes
Your code has leaked 48 bytes of memory. This means you have lost access to some blocks of memory before ending your program. Make sure you have freed all the memory you have allocated in your program.
48
Thread Error Analysis
Your program is analyzed for any kind of thread errors in this section. These errors are hard to find by manual debugging. For data race errors, you may see duplicate rows, as they are listed each time they happen.
Possible Data Race
There is a possiblity of data race in your code. You are using a block of memory on line 136 of your code, which conflicts with another thread's use of that block on line 130
Yes
Possible Data Race
There is a possiblity of data race in your code. You are using a block of memory on line 136 of your code, which conflicts with another thread's use of that block on line 130
Yes
Threads Execution Timeline
Here you can see the threads you have created along the time, and the locks they waited on, if any.
phase 3 of 3:
code analysis
(unbalanced)
Unbalanced (3 of 3)
In this test case your code is checked for handling unbalanced number of matrices.
Raw Input
7
2x2
1 1
1 1
2x2
1 1
1 1
2x2
1 1
1 1
2x2
1 1
1 1
2x2
1 1
1 1
2x2
1 1
1 1
2x2
1 1
1 1
Overall Result
Memory Problems
Number of problems with your memory usage. In case of errors, you can see more info in memory analysis section.
138
Compilation
Compilation succeeded.
Successful
Maliciousness
Your code was considered safe. Keep it this way.
Safe
Thread Problems
Errors found with your threads. In case of errors, you can see more info in thread error analysis section.
12
Memory Analysis
In this section your memory usage is analyzed. Use it to find out if your code leaks and/or has illegal accesses to memory.
Invalid Use of Memory
You tried to write to an invalid address on line 51 of your code.
Yes
Illegal Free
You tried to free an invalid block of memory on line 51 of your code. You may have freed this block before.
Yes
Illegal Free
You tried to free an invalid block of memory on line 123 of your code. You may have freed this block before.
Yes
Invalid Use of Memory
You tried to write to an invalid address on line 102 of your code.
Yes
Invalid Use of Memory
You tried to write to an invalid address on line 103 of your code.
Yes
Invalid Use of Memory
You tried to write to an invalid address on line 55 of your code.
Yes
Invalid Use of Memory
You tried to write to an invalid address on line 55 of your code.
Yes
Invalid Use of Memory
You tried to write to an invalid address on line 104 of your code.
Yes
Invalid Use of Memory
You tried to write to an invalid address on line 55 of your code.
Yes
Invalid Use of Memory
You tried to write to an invalid address on line 55 of your code.
Yes
Invalid Use of Memory
You tried to write to an invalid address on line 104 of your code.
Yes
Invalid Use of Memory
You tried to write to an invalid address on line 51 of your code.
Yes
Illegal Free
You tried to free an invalid block of memory on line 51 of your code. You may have freed this block before.
Yes
Illegal Free
You tried to free an invalid block of memory on line 123 of your code. You may have freed this block before.
Yes
Leaked Bytes
Your code has leaked 80 bytes of memory. This means you have lost access to some blocks of memory before ending your program. Make sure you have freed all the memory you have allocated in your program.
80
Thread Error Analysis
Your program is analyzed for any kind of thread errors in this section. These errors are hard to find by manual debugging. For data race errors, you may see duplicate rows, as they are listed each time they happen.
Possible Data Race
There is a possiblity of data race in your code. You are using a block of memory on line 136 of your code, which conflicts with another thread's use of that block on line 130
Yes
Possible Data Race
There is a possiblity of data race in your code. You are using a block of memory on line 136 of your code, which conflicts with another thread's use of that block on line 130
Yes
Threads Execution Timeline
Here you can see the threads you have created along the time, and the locks they waited on, if any.

atm machine simulation
phase 1 of 3:
submit your code
Submit your atm simulation code below. You can upload C/C++ codes:
When you did it, you will see your submission time.
The final submission will be used for delay calculation.

phase 2 of 3:
run your code
Here you can run your latest submission.
Be warned:
  • You can only run your code every 10 minutes.
  • If your code tries anything malicious, it will get killed*.
When you submit your code, you will see an option to run your code.
*
anyway your code will run in a sandboxed environment, in the middle of a desert. alone and helpless.

phase 3 of 3:
code analysis
You haven't run your code yet. Run your code in the previous section.
When running your code finishes, you will need to reload the page to see the results.
ATM tests take much longer. Be Patient.