Thread: the craziest damn error i've ever seen! help!

its about saving again. i have it totally complete except for two things. they are very hard to explain. its a windows error box that pops up, there are no compile errors. so the windows box pops up and says "dungeonofdoom.exe has encountered an error. sorry for any inconvenience.....". THen there is an option that says debug. I click that and then VC++6 pops up with my code in it, but in debug mode. then a box pops up and says "Unhandled exception in Dungeon of Doom.exe: 0xC0000005: Access Violation". I click ok and then you'll see the two pics that i attached, they are a pic of the screen in debug mode. please someone help me.

perhaps its this:

Code:

do
			{
			    if(search_weapon->id==weapon1)
				{
				    stop=1;
				}
			    if(stop!=1)
				{
			        search_weapon++;
				}
				cout<<search_weapon->id<<flush;
				_getch();
			}while(stop==0);

there is the code with the error. search_weapon is type 'pointer to WEAPON, or WEAPON*'. it is SUPPOSED to cycle through all the variables of type weapon. it starts at dagger (seach_weapon=&dagger) and dagger is of type WEAPON. I want it to cycle through all variables of type WEAPON. i printed out each value after doing search_weapon++, and i get these HUGE weird numbers. i think that's the problem. how would i search through all the variables of type WEAPON?

yes, ive confirmed it. i have a struct WEAPON. WEAPON dagger. WEAPON* seach_weapon=&dagger. dagger.id=1. WEAPON sword. sword.id=2. when i increment search_weapon i want it to go to the next variable of type WEAPON (sword). but it doesn't. how would i do this? i need to do it because i have to search all of those variables for a matching id. a linked list or something? i dont even know what that is. HELP PLEASE!

Did you try running it through the debugger?

it doesnt matter, and yes i did. but i've already concluded its just because its not cycline through the variables. i dont know where i got the idea of search_wepon++, but i need to be able to search through all the variables of type WEAPON in a loop, because it would be too horendous to check through ALL the variables, and less modular.