Re: The step over function of gdb enters header file code

[Kris Warkentin <kewarken@qnx.com>]

Try 'next' instead of 'step'.  This is a feature, not a bug - it's 
actually very handy to be able to step into headers in many cases.  
Alternatively, you could try compiling with -gstabs+.  The last time I 
checked, gcc wouldn't generate stabs debug info for headers.

cheers,

Kris

Daniel Simard wrote:

>Hi, 
>
>I am not sure if it is the right place to post those kings of questions,
>but if it is not please tell me where to post it.
>
>I am trying to debug an existing module that is using STL (string,
>vector etc...). When I break it the code, I want to trace it using the
>"step over" command of gdb, the debugger continually enters and break
>into STL header file code. I know that those header files are using
>template, but is it possible to tell gdb to not trace into system code
>when using "step over" command. I tried kdevelop and ddd debuggers and
>both are doing the same thing. My version of gdb is 6.1.
>
>Thanks
>___________________
>Daniel-Olivier Simard, eng. 
>Firmware Designer 
>Simpler Networks Inc.
>1840 TransCanada, Suite 100 
>Dorval, Québec, Canada, H9P 1H7
>Phone : (514) 684-2112 x354 
>Fax : (514) 684-2127
>
>  
>