User forums > Help

[SOLVED]Help using debugger

<< < (2/3) > >>

markons:
Hi, I have a similar problem, I use C::B 12.11 and the standard GCC compiler when I debug and when I open the debug-> debugging windows -> Watches, in the Watches window i dont have anything, there's no local variables and function arguments, nothing, only a blank window... i set a breakpoint and evrithing... Funny thing is when I do the same thing in C::B 10.05 i have normal Watches window with local variables and function arguments and everything works fine...
Can someone help me pls ???

oBFusCATed:

--- Quote from: markons on December 10, 2012, 06:43:35 pm ---Can someone help me pls ???

--- End quote ---
Have you read the change log? Forum search? You're probably the 100+th person to ask this question.

http://wiki.codeblocks.org/index.php?title=Debugging_with_Code::Blocks#In_12.11_or_latest_nightly_builds

joneewheelock:
Which path we need to take care of space? I am getting same issue (CB 16.01)

-g is used for compiling. Optimization is disabled and I am using C++11.

Active debugger config: GDB/CDB debugger:mingwDBG
Building to ensure sources are up-to-date
Selecting target:
Debug
Adding source dir: C:\Temp\collegeProject\
Adding source dir: C:\Temp\collegeProject\
Adding file: C:\Temp\collegeProject\Debug\collegeProject.exe
Changing directory to: C:/Temp/collegeProject/.
Set variable: PATH=.;C:\TDM-GCC-64\bin;C:\TDM-GCC-64;C:\Program Files\Java\jdk1.8.0_77\bin;C:\ProgramData\Oracle\Java\javapath;c:\Program Files (x86)\Intel\iCLS Client;c:\Program Files\Intel\iCLS Client;C:\Windows\System32;C:\Windows;C:\Windows\System32\wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\IPT;C:\wamp\www;C:\Program Files (x86)\MySQL\MySQL Fabric 1.5 & MySQL Utilities 1.5;C:\Program Files (x86)\MySQL\MySQL Fabric 1.5 & MySQL Utilities 1.5\Doctrine extensions for PHP;C:\Program Files (x86)\OpenSSH\bin;C:\Users\Mahesha\AppData\Local\Microsoft\WindowsApps
Starting debugger: C:\MinGW\bin\gdb.exe -nx -fullname -quiet  -args C:/Temp/collegeProject/Debug/collegeProject.exe
done
Registered new type: wxString
Registered new type: STL String
Registered new type: STL Vector
Setting breakpoints
Debugger name and version: GNU gdb (GDB) 7.6.1
Starting the debuggee failed: No executable specified, use `target exec'.
Debugger finished with status 0

oBFusCATed:

--- Quote from: joneewheelock on January 26, 2018, 06:17:41 am ---Which path we need to take care of space? I am getting same issue (CB 16.01)

--- End quote ---
I don't think you're getting any of the two issues reported in the topic.
It is something else, but we need bigger log.
Please enable full debugger log and post it here.
Please use code tags (the # button).

stahta01:
Bad compiler toolchain installation is my guess.


--- Code: ---Set variable: PATH=.;C:\TDM-GCC-64\bin;C:\TDM-GCC-64;C:\Program Files\Java\jdk1.8.0_77\bin;C:\ProgramData\Oracle\Java\javapath;c:\Program Files (x86)\Intel\iCLS Client;c:\Program Files\Intel\iCLS Client;C:\Windows\System32;C:\Windows;C:\Windows\System32\wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\IPT;C:\wamp\www;C:\Program Files (x86)\MySQL\MySQL Fabric 1.5 & MySQL Utilities 1.5;C:\Program Files (x86)\MySQL\MySQL Fabric 1.5 & MySQL Utilities 1.5\Doctrine extensions for PHP;C:\Program Files (x86)\OpenSSH\bin;C:\Users\Mahesha\AppData\Local\Microsoft\WindowsApps
Starting debugger: C:\MinGW\bin\gdb.exe -nx -fullname -quiet  -args C:/Temp/collegeProject/Debug/collegeProject.exe
done
--- End code ---

He is using C:\MinGW\bin\gdb.exe as the debugger; but, compiling likely with C:\TDM-GCC-64 as the toolchain.

Tim S.

Navigation

[0] Message Index

[#] Next page

[*] Previous page