CODEWITHSUNDEEP
parsingc++11segmentation-fault
J P
J P

Reputation: 1

Where does a segmentation fault occur if the debugger points to a function definition?

To elaborate, I am currently writing a program that requires a function that is provided by the professor. When I run the program, I get a segmentation fault, and the debugger I use (gdb) says that the segmentation fault occurred at the definition of the function that, like I said, was provided by the professor.

So my question here is, is the definition itself causing the fault, or is it somewhere else in the program that called the function causing the fault?

I attempted to find a spot in the program that might have been leading to it, such as areas that might have incorrect parameters. I have not changed the function itself, as it is not supposed to be modified (as per instructions). This is my first time posting a question, so if there is any other information needed, please let me know.

The error thrown is as follows:

Program received signal SIGSEGV, Segmentation fault. .0x00401450 in Parser::GetNextToken (in=..., line=@0x63fef0: 1) at PA2.cpp:20 20 return GetNextToken(in, line);

The code itself that this is happening at is this:

static LexItem GetNextToken(istream& in, int& line) {
    if( pushed_back ) {
        pushed_back = false;
        return pushed_token;
    }
    return GetNextToken(in, line);
}

Upvotes: 0

Views: 28

Answers (1)

mzm
mzm

Reputation: 51

Making many assumptions here, but maybe the lesson is to understand how the stack is affected by a function call and parameters. Create a main() function, that call the professor's provided function and trace the code using dbg, looking at the stack.

Upvotes: 0

Related Questions