Not sure if this should go in trouble shooting but recently while debugging codelite opens header files for the standard c++ library when stepping into a function associated with said header file when preferably it use to just like output if it was cout and go to the next line code. What’s making this difficult is that a while ago I updated codelite and I’m uncertain if codelite had the -g or -gdwarf or neither argument for compiling options as the default since the only option I added was pedantic errors and the standard to use for c++. I’ve tried searching everywhere and it apparently isn’t suppose to open the standard library header files during debugging. The other compiler arguments are -Wall, -std=c++20, pedantic errors, and the option that optimizes for debugging. What I’d like to know is if the standard c++ library h files are suppose to open during debugging and if not what are possible solutions considering the information I have given?
Debugging opening standard library h files
-
- CodeLite Curious
- Posts: 1
- Joined: Sat Jul 29, 2023 2:15 am
- Genuine User: Yes
- IDE Question: C++
- Contact:
- Jarod42
- CodeLite Expert
- Posts: 240
- Joined: Wed Sep 30, 2009 5:54 pm
- Genuine User: Yes
- IDE Question: C++
- Location: France
- Contact:
Re: Debugging opening standard library h files
I would say it is gdb configuration, see tell-gdb-to-skip-standard-files
And in Codelite, possibly in "Settings"/"GDB Settings"/"Startup command".