Thread: help for debugging my code

EDIT: I was busy writing this when you posted the location files, so disregard that part. The rest, however, stands.
EDIT 2: Removed unnecessary compiler error messages

Here's what I get when I compile your program:

Code:

$ make foo
gcc -Wall -Wunreachable-code -ggdb3  -lm -lpthread  foo.c   -o foo
foo.c:2:21: error: windows.h: No such file or directory
foo.c:4:19: error: conio.h: No such file or directory
foo.c:5:23: error: location2.h: No such file or directory
foo.c: In function ‘main’:
foo.c:55: error: ‘HANDLE’ undeclared (first use in this function)
foo.c:55: error: (Each undeclared identifier is reported only once
foo.c:55: error: for each function it appears in.)
foo.c:55: error: expected ‘;’ before ‘hStdout’
foo.c:56: error: ‘hStdout’ undeclared (first use in this function)
foo.c:56: warning: implicit declaration of function ‘GetStdHandle’
foo.c:56: error: ‘STD_OUTPUT_HANDLE’ undeclared (first use in this function)
foo.c:58: warning: implicit declaration of function ‘init_console_functions’
foo.c:254: warning: suggest parentheses around assignment used as truth value
foo.c:256: warning: suggest parentheses around assignment used as truth value
foo.c:258: warning: suggest parentheses around assignment used as truth value
foo.c:297: warning: implicit declaration of function ‘clrscr’
foo.c:353: warning: suggest parentheses around assignment used as truth value
foo.c:355: warning: suggest parentheses around assignment used as truth value
foo.c:357: warning: suggest parentheses around assignment used as truth value
foo.c:438: warning: suggest parentheses around assignment used as truth value
foo.c:440: warning: suggest parentheses around assignment used as truth value
foo.c:442: warning: suggest parentheses around assignment used as truth value
foo.c: In function ‘Drawing_mushroom’:
foo.c:486: error: ‘HANDLE’ undeclared (first use in this function)
foo.c:486: error: expected ‘;’ before ‘hStdout’
foo.c:487: error: ‘hStdout’ undeclared (first use in this function)
foo.c:487: error: ‘STD_OUTPUT_HANDLE’ undeclared (first use in this function)
foo.c:489: warning: implicit declaration of function ‘gotoxy’
foo.c:490: warning: implicit declaration of function ‘SetConsoleTextAttribute’
foo.c: In function ‘Drawing_flower’:
foo.c:502: error: ‘HANDLE’ undeclared (first use in this function)
foo.c:502: error: expected ‘;’ before ‘hStdout’
foo.c:503: error: ‘hStdout’ undeclared (first use in this function)
foo.c:503: error: ‘STD_OUTPUT_HANDLE’ undeclared (first use in this function)
...
make: *** [foo] Error 1

1. I'm guessing most of the "undeclared" issues are due to you not providing us with location2.h and the fact that I don't have windows.h and conio.h since I use Linux.
2. All the "suggest parentheses" ones seem to be because you are using = instead of ==.
3. fflush(stdin) results in undefined behavior. Read this link.
4. Your while loop around line 98 while ((fscanf(...) != EOF) is wrong, don't check against EOF. You need to check whether it successfully read a char. fscanf returns the number of things it successfully scanned (1 in your case). Try while (fscanf() != 1).
5. You don't check all your error conditions (e.g. malloc, fopen). Sometimes, when you encounter a critical error, like malloc failing, you continue your program anyway, begging for a seg fault.
6. You use lots of printf's for debugging, but printf is buffered, so your debug "ok" prints might not show up when you expect them, leading you to think the problem is elsewhere. You need to print a newline, flush stdout, or use stderr for debug prints.
7. It's too late now, but you really should have broken your main function up into more smaller functions, it would be much easier to debug that way.
8. There's lots more little things, but you wont have the time, and I don't feel like reading through every line of your code.

You say you think your "storing" code is wrong. What code, exactly, would that be? Nowhere in your comments, or in the name of functions or variables, do you use the word storing, so I can't locate the "storing" code. Also, tell us exactly what is wrong with it. Does the program crash? Does it run but give strange output? Does it "freeze"? We need more info.

Re - post #10
You should select option 3 - "Debug program".

That will drop you in the debugger, pointing at the offending line of code.

From there, you examine relevant variables, and try to construct (in your head) how the program got into that state.
When you understand that, you can set about fixing it.

By my estimation, times up!
Put down your keyboard, step away from the mouse.

FYI, rolling into a forum with only hours to go and 100's of lines of code to look at is seldom productive.

Try to leave more time (at least a day) before waiting to post when you're stuck.

It also helps to write AND test as you go.
A development process
Expecting the whole thing to work right at the last minute is folly.