User forums > Help

Debugger cannot open files

<< < (4/4)

Jenna:
I just tested it on vista with a wizard-created standard-project, no special settings, and debugging into wxWidgets works fine.

Self build (of course) C::B from trunk (r5923).

wxWidgets 2.8.10 build the same way as yours.
All build with TDM's gcc 4.4.1-2, debugger is gdb 7.02.

The project is in "c:\new\tmp\testtt", wxWidgets is below "c:\wxwidgets-2.8.10", that's also the base path of the global variable "wx", all other fields of the settings for "wx" are left empty.

carrejans:
Still haven't found a solution to my problem.
I make use of wxwidgets 2.9.0 and last nightly build of codeblocks.

ollydbg:

--- Quote from: carrejans on November 30, 2009, 03:23:47 pm ---Still haven't found a solution to my problem.
I make use of wxwidgets 2.9.0 and last nightly build of codeblocks.

--- End quote ---

Both jens and me have no problem debug into the wx source code. So I still suggest you can use wxWidgets 2.8.10.(because I havn't tried 2.9.0).

The last suspect is : did you have some space between the folder names? such as your wxWidgets library path is :

C:\XXXXX  XXXXX\

This may cause some problems in my opinion GDB can't debug into a source file with space in full path names. :D

carrejans:

--- Quote from: ollydbg on November 30, 2009, 03:50:03 pm ---
--- Quote from: carrejans on November 30, 2009, 03:23:47 pm ---Still haven't found a solution to my problem.
I make use of wxwidgets 2.9.0 and last nightly build of codeblocks.

--- End quote ---

Both jens and me have no problem debug into the wx source code. So I still suggest you can use wxWidgets 2.8.10.(because I havn't tried 2.9.0).

The last suspect is : did you have some space between the folder names? such as your wxWidgets library path is :

C:\XXXXX  XXXXX\

This may cause some problems in my opinion GDB can't debug into a source file with space in full path names. :D

--- End quote ---

No, no spaces in path.

I use some things from 2.9, that don't exist in 2.8.10.  :?

Jenna:
After reading this thread again, I can confirm this problems.
I can debug into wWidgets, that means set a breakpoint in my code and then step into wxWidgets code.

Jumping into wxWidgets sources from the callstack does indeed not work.
The problem is, that wxWidgets is not compiled with full, but with relative paths, so C:::B does not know where to look for ../src/xxx.cpp.

Navigation

[0] Message Index

[*] Previous page