CodeBlocks - my program crashes on file import (debugging).

Hi, im using CodeBlocks and have only changed code that follows on from this section. My program runs up to a importing all data and some outputs.
But if i run it in debug mode now. It crashes Codeblocks at file import.

The code i have.

Code:

int main(int argc, char* argv[]) {

    GJCType menu;

    char stringInput[MENU_INPUT + EXTRA_SPACE];
    int menuSelection = 0;
    char *ptr;

    systemInit(&menu);

    if (argc == 3) {
        loadData(&menu, argv[1], argv[2]);
    } else {
        fprintf(stderr, "File import incorrect should be menu.dat submenu.dat");
        exit(EXIT_FAILURE);
    }

Code:

int loadData(GJCType* menu, char* menuFile, char* submenuFile) {

    FILE *menuInput;
    FILE *submenuInput;
    char lineBuffer[MAX_LINE_LENGTH+1];

    int validation;

    printf("IMPORTING DATA... from Files\n");
    menuInput = fopen(menuFile, "r");  /* Crashes CodeBlocks here */
    submenuInput = fopen(submenuFile, "r");

Does it run outside the debugger?
Are you building it with debugging information included?

Runs when i do a 'Build and Run' but not with the Debugger.

Originally Posted by TonyG

Runs when i do a 'Build and Run' but not with the Debugger.

Ok... so you're doing a debug build?

Yes.. it matters... release builds are not compatible with the debugger.

> menuInput = fopen(menuFile, "r"); /* Crashes CodeBlocks here */
1. You mean the debugger is pointing at this line of code?

> printf("IMPORTING DATA... from Files\n");
2. Or are you just IMPLYING that this is the location of the crash, based on the fact that this line is the last line printed?

Because if it's door number 2, then you need to realise that stdout is buffered, and the program could have gone past where you think it has gotten to before actually crashing.

Debugger hangs at the line of code - menuInput = fopen(menuFile, "r"); following the debugger line by line.

Any chance that this could be caused by malloc at some point further in my code? Because that was the only thing i messed with before this happened.

Well... you could try investigating that... it's usually the last thing you mess with that causes the problems.

Old technician's adage... "If it ain't broke, don't fix it. If it is broke, know when to stop fixing it."

So is the code you posted the ACTUAL code that has run up to that point?

You see, you mentioned malloc, but there is no malloc in any of the code you posted (how do you know malloc is involved).

FWIW, abusing malloc can easily cause all kinds of random effects at any later point in the code.

Which is why we make a noise about whether this is all your code under test, or whether you just edited out all the interesting stuff, and just posted where you thought the problem was.