| # | User | Rating |
|---|---|---|
| 1 | tourist | 3993 |
| 2 | jiangly | 3743 |
| 3 | orzdevinwang | 3707 |
| 4 | Radewoosh | 3627 |
| 5 | jqdai0815 | 3620 |
| 6 | Benq | 3564 |
| 7 | Kevin114514 | 3443 |
| 8 | ksun48 | 3434 |
| 9 | Rewinding | 3397 |
| 10 | Um_nik | 3396 |
| # | User | Contrib. |
|---|---|---|
| 1 | cry | 167 |
| 2 | Um_nik | 163 |
| 3 | maomao90 | 162 |
| 3 | atcoder_official | 162 |
| 5 | adamant | 159 |
| 6 | -is-this-fft- | 158 |
| 7 | awoo | 156 |
| 8 | TheScrasse | 154 |
| 9 | Dominater069 | 153 |
| 9 | nor | 153 |
I would like to invite you to participate in the online mirror of the Croatian Olympiad in Informatics which is held this Saturday.
The problemset will consist of 3-5 IOI stlye tasks and you will have 5 hours to solve them. The expected difficulty is greater than usual COCI rounds, but lesser than IOI.
Click here to see where the coding begins in your timezone.
Everyone has had a bug in their code because of accessing out of array bounds. However, in some cases, the program will run as expected.
I have two examples from today's contest: problem B — 24829988 problem C — 24831518
In both of these problems, I had stupid bugs. For problem B, it's possible that the argument k of the function is zero and this line
if (ind == f[k-1]) return (int) (n % 2)
will access f[ - 1] which is undefined.
I have found this bug, and after some stress testing locally and on CodeForces, I decided not to resubmit because it seemed fine.
Now, in problem C, I iterated up to 1029 and the value of i xor x can become larger than the size of the array. However, this is only an issue if that piece of memory is not used by the process and it will result in seg fault.
Otherwise, nothing will be changed because we add zero.
I only found this bug while I was trying to hack someone else's solution so I couldn't resubmit and I was pretty sure it was going to fail system tests because locally it resulted in seg fault for some cases.
To my surprise, both submissions were actually successful, and my F failed (but that's irrelevant to this post xD) My question is this: what do you usually do when you find a bug like this during the contest and do you stress test your solutions before submitting to prevent it?
I encountered an unusual runtime error during today's Div 2 round on problem D. http://codeforces.net/contest/706/problem/D
I implemented a simple trie, and received runtime error on test 1. http://codeforces.net/contest/706/submission/19803196
After some more submissions, I got to this: http://codeforces.net/contest/706/submission/19805829
With a couple of custom invocations, I narrowed the problem down to function mx. Implementing it a bit differently, I got AC. http://codeforces.net/contest/706/submission/19808959
After the contest, I tried submiting my code to several other sites: SPOJ, UVa, ideone. I also ran the code locally both on Windows and Linux. Out of all of these, CodeForces was the only platform on which the program crashed.
Is there a bug in the compiler, or am I missing something?
