submit your code
run your code
Be warned:
- You can only run your code every 10 minutes.
- If your code tries anything malicious, it will get killed*.
code analysis
(simple)
Simple (1 of 3)
In this test case two matrices are multiplied.
8 | 2 | 3 | 4 |
9 | 3 | 5 | 7 |
2 | 3 |
4 | 5 |
6 | 7 |
9 | 3 |
78 | 67 |
123 | 98 |
You should only create two threads for row multiplication.
2
2x4
8 2 3 4
9 3 5 7
4x2
2 3
4 5
6 7
9 3
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 |
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 |
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 |
Here you can see the threads you have created along the time, and the locks they waited on, if any.
code analysis
(moderate)
Moderate (2 of 3)
In this test case four matrices are multiplied.
1 | 1 |
1 | 1 |
1 | 1 |
1 | 1 |
1 | 1 |
1 | 1 |
1 | 1 |
1 | 1 |
8 | 8 |
8 | 8 |
4
2x2
1 1
1 1
2x2
1 1
1 1
2x2
1 1
1 1
2x2
1 1
1 1
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 |
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 |
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 |
Here you can see the threads you have created along the time, and the locks they waited on, if any.
code analysis
(unbalanced)
Unbalanced (3 of 3)
In this test case your code is checked for handling unbalanced number of matrices.
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
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 |
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 |
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 |
Here you can see the threads you have created along the time, and the locks they waited on, if any.