Bug #12133 2007-10-08 02:15
jfemiani
Relative Include Directories Mess with GDB
On Windows using MinGW and gdb, if relative paths are used for include files when compiling, then GDB fails to recognize the filename when breakpoints are set.
I noticed that a partial fix for this is in place because of the 'use full filenames for source files' option under compiler/debugger settings, but GDB has the same problem with include search directories.
In particuler, if you use something like:
-I../../include
Then when you step theough it with gdb you current source file is listed as:
C:/my_project/foo/bar/../../include/foo.hpp
instead of
C:/my_project/foo/bar/include/foo.hpp
and if you try to set a break point in codeblocks it can not find C:/my_project/foo/bar/include/foo.hpp.
This seems to be a problem with GDB rather than codeblocks, but codeblocks has attempted a workaround and this bug addresses the issues with that workaround in some cases.
This appears like it may possibly be related to Bug #10454.
- Category
- Compiler
- Group
- Status
- Open
- Close date
- Assigned to