Mirror of the gdb mailing list
 help / color / mirror / Atom feed
* The step over function of gdb enters header file code
@ 2005-02-07 13:49 Daniel Simard
  2005-02-07 15:10 ` Kris Warkentin
  0 siblings, 1 reply; 2+ messages in thread
From: Daniel Simard @ 2005-02-07 13:49 UTC (permalink / raw)
  To: gdb

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



^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: The step over function of gdb enters header file code
  2005-02-07 13:49 The step over function of gdb enters header file code Daniel Simard
@ 2005-02-07 15:10 ` Kris Warkentin
  0 siblings, 0 replies; 2+ messages in thread
From: Kris Warkentin @ 2005-02-07 15:10 UTC (permalink / raw)
  To: Daniel Simard; +Cc: gdb

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
>
>  
>


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2005-02-07 14:54 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2005-02-07 13:49 The step over function of gdb enters header file code Daniel Simard
2005-02-07 15:10 ` Kris Warkentin

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox