User forums > Help

Can't set GDB breakpoints in other directories

<< < (2/3) > >>

killerbot:
I feel we are something missing in our understanding of gdb. Or GDB is missing a serious feature ;-)

MortenMacFly:

--- Quote from: killerbot on January 11, 2007, 11:01:19 am ---I feel we are something missing in our understanding of gdb. Or GDB is missing a serious feature ;-)

--- End quote ---
This I honestly believe, too. ;-)

mandrav:

--- Quote from: MortenMacFly on January 11, 2007, 11:06:50 am ---
--- Quote from: killerbot on January 11, 2007, 11:01:19 am ---I feel we are something missing in our understanding of gdb. Or GDB is missing a serious feature ;-)

--- End quote ---
This I honestly believe, too. ;-)

--- End quote ---

I can explain exactly what happens if you want but the problem is actually how gdb looks for source files. If you ask me, having looked at it extensively, it's a borked implementation in gdb. It all stems from the fact that for gdb C:\Devel\foo\bar\..\foo.cpp is a different file from C:\Devel\foo\foo.cpp.

The only solution I can think of is for C::B to use full file path when compiling (not linking) a file. Have to test it though.

Game_Ender:
It might be slower but I thought is a best practice to at least normalize and at best make absolute paths that you pass off to other tools, because you can make no assumptions about how they handle them.   I do agree GDB should really do the same thing and normalize all paths before comparison.

mandrav:
Since revision 3491, absolute filenames are used when compiling source files. I tested it and debugging works fine this way :).

This means that you should rebuild your libraries (at least those that you 're having trouble putting breakpoints into when debugging other projects).

Navigation

[0] Message Index

[#] Next page

[*] Previous page