User forums > Help

Problem with own makefile and GDB is back again

<< < (2/2)

kai7:
Good for you. :-)  Unfortunately I am already using the most recent version (6.3.2). One thing I found out is quite interesting: An "info source" gives this:


--- Code: ---(gdb) info source
Current source file is ../../src/MainWin.cpp
Compilation directory is d:/Daten/C++/FrontDesign/FrontDesign.wx/src/
Located in d:/Daten/C++/FrontDesign/FrontDesign.wx/src/../../src/MainWin.cpp
--- End code ---

And so a


--- Code: ---break d:/Daten/C++/FrontDesign/FrontDesign.wx/src/../../src/MainWin.cpp:xxx
--- End code ---

is working as well. So it seems to be a relative-absolute path converting problem within the gdb. So I wouldn't blame CB for this problem. But I am hoping to work around it with CB. ;-)     

mandrav:

--- Quote ---So it seems to be a relative-absolute path converting problem within the gdb. So I wouldn't blame CB for this problem. But I am hoping to work around it with CB.
--- End quote ---

It's already worked out for you. Just rebuild your project (and any libraries linked to it and you compiled them yourself) and the problem will be gone. This is the reason why absolute filenames are used now when compiling: so gdb can find the files.

kai7:

--- Quote ---It's already worked out for you. Just rebuild your project (and any libraries linked to it and you compiled them yourself) and the problem will be gone. This is the reason why absolute filenames are used now when compiling: so gdb can find the files.
--- End quote ---

Yes, if I would compile it with C::B. But I use my own makefile which is created with an automake script. There the relative paths are still used. Until now I didn't find a way to use absolute paths with such a makefile...

kai7:
Why not doing the obvious. :oops: I just ran the configure script using the absolute path of it. No I have a makefile with absolute paths in it and all my problems are solved. Sorry for the "ado about nothing".


 

Navigation

[0] Message Index

[*] Previous page