Thread: Help with my linked list

You're running into problem after problem because you're not learning enough about what your program actually does. Seriously, run the program in a debugger and step through it one line at a time.
What you're doing is like coming up with a bunch of directions about precisely what turns to take to your cab driver then going to sleep and waking up at the wrong destination. What you need to do is the equivalent of staying awake to see where he makes a wrong turn so that you can correct your directions. That equivalent change to staying awake is to use the debugger.
You step through the code one line at a time and see where it goes wrong. Tell us what programming environment you're using so we can help you to use your debugger, then you can stop programming in the dark.

Otherwise known as "Give a man a fish and he'll eat for a day; teach a man to fish and ...".
'cause I think I'm done handing out fishes for today...

Originally Posted by evildotaing

I am not good in using a debugger. I did not learn how to use it.

"did not learn" doesn't really make sense here unless you're about to quit programming forever.
Learning to use a debugger is not optional for programming. All you can say is that you "have not learnt how yet".

Using a debugger is absolutely essential to being a programmer. There is no avoiding it. Tell us what programing environment you are using and we will help you get started.

See that "debug" menu in the IDE? That's your best friend.
There are several important commands, and I will teach you a few.

Step into: tells the debugger to execute one line of code and then stop. If the line is a function, then the debugger jumps into the function and then stops.
Step over: tells the debugger to execute one line of code and then stop. If the line is a function, it executes the entire function, then stops.
Step out: tells the debugger to continue executing the function you're currently in, and then stop once it's finished (has returned).

Breakpoints can be used to tell the debugger to stop at a specific point in your program. To create a breakpoint, left-click in the margin next to the line you want it to stop at.
To start debugging, choose debug -> start debugging. The debugger will run the program up to the next breakpoint. Alternatively, you can choose step in to have the debugger stop at the first line of your code.

You can hover your mouse over variables to see their values. You can also make code changes and recompile that without having to restart. You will find that under Debug -> apply code changes.
You may find the watch window (bottom left), autos and local variables to be useful to watch or see values of variables.
The call stack shows what functions has called what and can be found in the lower right bottom.

Experiment with these functions and see what you can learn.