![]() Starting the debuggee failed: No executable specified, use `target exec'. 1 didn't work, as in, the install didn't work or it didn't fix your problem what does the debug tab say have you tried to build/run your program from the command line Joshua Besneatte at 7:55 what i meant was that the package was already installed. No executable specified, use `target exec'. Use the "file" command.īreakpoint 2 ("C:/CodeBlocks_Projects/test-debug-2/Untitled2.cpp:44") pending. > break "C:/CodeBlocks_Projects/test-debug-2/Untitled2.cpp:44" Source directories searched: C:/CodeBlocks_Projects/test-debug-2 $cdir $cwd > directory C:/CodeBlocks_Projects/test-debug-2/ Type "apropos word" to search for commands related to "word".ĭebugger name and version: GNU gdb (GDB) 7.9.1 Type "show configuration" for configuration details.įor bug reporting instructions, please see:įind the GDB manual and other documentation resources online at: There is NO WARRANTY, to the extent permitted by law. This is free software: you are free to change and redistribute it. ![]() License GPLv3+: GNU GPL version 3 or later ![]() "C:/CodeBlocks_Projects/test-debug-2/bin/Debug/test-debug-2.exe": not in executable format: File format not recognizedĬopyright (C) 2015 Free Software Foundation, Inc. Starting debugger: C:\CodeBlocks\MinGW\bin\gdb32.exe -nx -fullname -quiet -args C:/CodeBlocks_Projects/test-debug-2/bin/Debug/test-debug-2.exe Working dir : C:\CodeBlocks_Projects\test-debug-2 Is it possible with Code::Blocks A: Yes, you can. Q: My project should be compiled with a custom makefile. C:\cygwin64\bin C:\cygwin64 C:\Program Files (x86)\Intel\iCLS Client C:\Program Files\Intel\iCLS Client C:\Program Files\Dell\DW WLAN Card C:\Windows\System32 C:\Windows C:\Windows\System32\wbem C:\Windows\System32\WindowsPowerShell\v1.0 c:\Program Files\WIDCOMM\Bluetooth Software c:\Program Files\WIDCOMM\Bluetooth Software\syswow64 C:\Program Files\Intel\Intel(R) Management Engine Components\DAL C:\Program Files (x86)\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\IPT C:\Windows\System32\OpenSSH C:\go\bin C:\Program Files\Git\cmd C:\Program Files\nodejs C:\Users\Chooi\AppData\Local\Microsoft\WindowsApps C:\Users\Chooi\go\bin C:\Users\Chooi\AppData\Roaming\npm C:\Program Files\Sublime Text 3 C:\Users\Chooi\AppData\Local\Programs\Microsoft VS Code\bin C:\Users\Chooi\AppData\Local\Programs\Python\Python37-32 C:\Users\Chooi\AppData\Local\Programs\Python\Python37-32\Scripts C:\nukeĬommand-line: C:\CodeBlocks\MinGW\bin\gdb32.exe -nx -fullname -quiet -args C:/CodeBlocks_Projects/test-debug-2/bin/Debug/test-debug-2.exe Some provided with the default Code::Blocks installation are GNU GCC (MinGW/Cygwin), MS Visual C++ Free Toolkit 2003, Borland's C++ Compiler 5.5, DigitalMars Free Compiler., OpenWatcom, Small Device C Compiler (SDCC) and others. Active debugger config: GDB/CDB debugger:Defaultīuilding to ensure sources are up-to-dateĪdding source dir: C:\CodeBlocks_Projects\test-debug-2\Īdding file: C:\CodeBlocks_Projects\test-debug-2\bin\Debug\test-debug-2.exeĬhanging directory to: C:/CodeBlocks_Projects/test-debug-2/.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |