| # | User | Rating |
|---|---|---|
| 1 | Radewoosh | 3611 |
| 2 | jiangly | 3597 |
| 3 | Benq | 3593 |
| 4 | ecnerwala | 3584 |
| 5 | orzdevinwang | 3570 |
| 6 | cnnfls_csy | 3569 |
| 7 | tourist | 3565 |
| 8 | maroonrk | 3487 |
| 9 | gyh20 | 3447 |
| 10 | Rebelz | 3409 |
| # | User | Contrib. |
|---|---|---|
| 1 | maomao90 | 174 |
| 2 | awoo | 164 |
| 3 | adamant | 162 |
| 4 | TheScrasse | 159 |
| 5 | nor | 158 |
| 6 | maroonrk | 156 |
| 7 | -is-this-fft- | 151 |
| 8 | SecondThread | 147 |
| 9 | orz | 146 |
| 10 | pajenegod | 145 |
Strange segfault on SPOJ KQUERY
Here is my AC code: https://hastebin.com/ewobuzater.cpp
It uses offline BIT + sorting.
Here is the strange thing: que[200001] works perfectly fine, but if you change it to que[200000] it will segfault. However, it is zero based indexing and q is at max 200000.
Can anyone think of a case where que[200000] faces out of bound access?
