gdb debug function not in the call stack

Question

I have a code snippet similar to this :

int test( /* some arguments */)
{
    ret = func(/* some arguments */)
    if (ret < 0) 
    {
       /* do this */
    }

    /* do this */

    return ret;
}

the function func is returning -1 for some erroneous condition inside the function. This erroneous condition occurs once in 100 times the test function is called - so I put breakpoint in if (ret < 0) line. Now I want to debug what's going on inside the function func(). How do I do it when the breakpoint is hit in test function at the said line.

Can you move your breakpoint(s) to every error branch in func instead? — simonc
– simonc, Commented Dec 27, 2012 at 9:23
Another fine example why a function shall only have one exit point. — alk
– alk, Commented Dec 27, 2012 at 17:19

Karthik T · Accepted Answer · 2012-12-27 09:23:01Z

2

I would put a break point at

return -1;

within the function itself. In the way you are doing, the stack frame of the function would have been destroyed already. You COULD run the function again with the same arguements if you can move the code pointer, but if the function has side effects, it may not react the same way. I am not sure how to do it though, perhaps it needs the jump command.

answered Dec 27, 2012 at 9:23

Karthik T

32.1k7 gold badges71 silver badges92 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

Shraddha Over a year ago

there are may such returns in the function func()

Karthik T Over a year ago

@shraddha as long as you can see the code of the function, and you are unable to rerun the function with the same arguements deterministically, I see no other option.

JasonD · Accepted Answer · 2012-12-27 10:41:33Z

0

Is the behaviour deterministic? If so, breakpoint hit-counters are good for this. You can set a very large count breakpoint somewhere before the error is generated, break also on the error being returned, look at the counter, and then change the count to break at count-1. Then you can then debug the error as it occurs, and the breakpoint can be anywhere in the code, not just at the exact point or error.

Conditional breakpoints are underused...

edited Dec 27, 2012 at 10:41

answered Dec 27, 2012 at 9:46

JasonD

16.6k2 gold badges31 silver badges44 bronze badges

Collectives™ on Stack Overflow

gdb debug function not in the call stack

2 Answers 2

2 Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

2 Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related