You are on page 1of 1

BETA TESTING - Code Debugging Event You have it, but can you "do" it ?

No no, you can't sweep it under the rug, no rest for you until you find the bug. Test your debugging skills in this mind shaking,nerve-racking competition where you have to find the "mole in the hole". "Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it." -- Brian Kernighan In this code debugging event participants are required to find the arbitrary(of any nature)bugs in the code (given either in C or in C++) and correct them. The team with the highest score wins. >>This competition will be of two rounds. Round 1: (45 minutes)

A preliminary multiple choice round to test the analytical and technical depth of the participants in the field of programming. All question will be either in C or in C++. Round 2: (1 hr) (IDE provided: Code Blocks)

On-System code debugging where teams will be given C or C++ codes which they have to test and debug within a specified time limit.Successfully executing all the programs of that round to give the desired output within the total allotted time will be considered as the solution. Each problem will have separate scores and there will be time based scores too. All other evaluation criteria and detailed scoring scheme will be notified during the event.There will be a bonus question for the first 2 teams who complete all the given tasks and have the highest scores. The team with the highest overall score of all rounds combined (Round 1 + 2 ) will be adjudged winner. Round 2 will have maximum weightage followed by Round 1. Rules & Evaluation: 1) Each team can have at most two members. 2) No two teams can have a common member. 3) For Round 2: Teams will be allotted systems for running their codes, which they must use for debugging and execution. 4) None of the participants should talk with/communicate/help any other participant during the event, which will lead to immediate disqualification of both teams involved. 5) Teams should NOT modify any settings/data already present in the system allotted to them. Any undesired behaviour in this regard will lead to immediate disqualification from the event. 6) No special header files/includes should be used unless otherwise mentioned in the problem statement/code block. In case of any queries about what to use, please seek help from the event coordinator/organizer. 7) Teams are not allowed to access/open/execute/run any other programs/applications during the event. 8) The decision of the judges/panel would be final and binding and no communication will be entertained in this respect.

Event Organizer: Prasoon Saurav (609/07)