User forums > Help

compiler/debug problem with adding flag option (no debugging symbols found)

(1/3) > >>

Tommi:
Hello guys,

i've got a problem while trying to debug the program i wrote.

I can't use "watches", after long search i figured out that this is a cause of missing debug symbols.
So i searched how to fix this. Unfortunately i have no idea where and how to add this -g,
cause i use code blocks for the first time and the flag "produce debug symbols(-g)" is not listed in "Settings -> compiler -> compiler flags"

So i tried to add this flag by hand, not working, i add it in "other compiler options" and just receive the message:


--- Code: ---||=== Build: Debug in Complexe_rechnung (compiler: Borland C++ Compiler (5.5, 5.82)) ===|
||Error E2074: Value after -g or -j should be between 0 and 255 inclusive|
||Error E2075: Incorrect command line option: -g|
||=== Build failed: 2 error(s), 0 warning(s) (0 minute(s), 0 second(s)) ===|

--- End code ---

I'm using Win7 64bit
Code::Blocks 16.01

Thanks for your help!

stahta01:
Post a full re-build log.
http://wiki.codeblocks.org/index.php/FAQ-Compiling_%28errors%29#Q:_How_do_I_troubleshoot_a_compiler_problem.3F

Edit: I do NOT think Code::Blocks supports debugging with Borland Compiler.

Tommi:
I guess u mean this log? Copyed out from "build log" after re-build, as explained in the FAQ


--- Code: ----------------- Clean: Debug in Complexe_rechnung (compiler: Borland C++ Compiler (5.5, 5.82))---------------

Cleaned "Complexe_rechnung - Debug"

-------------- Build: Debug in Complexe_rechnung (compiler: Borland C++ Compiler (5.5, 5.82))---------------

bcc32.exe -q -w  -v    -ID:\Programme\Borland\BCC55\Include -oobj\Debug\input.obj -c input.c
input.c:
bcc32.exe -q -w  -v    -ID:\Programme\Borland\BCC55\Include -oobj\Debug\my_complex.obj -c my_complex.c
my_complex.c:
bcc32.exe -q -w  -v    -ID:\Programme\Borland\BCC55\Include -oobj\Debug\output.obj -c output.c
output.c:
bcc32.exe -q -w  -v    -ID:\Programme\Borland\BCC55\Include -oobj\Debug\testfile.obj -c testfile.c
testfile.c:
ilink32.exe -q -ap  -v  -LD:\Programme\Borland\BCC55\Lib -LD:\Programme\Borland\BCC55\Lib\PSDK c0x32 obj\Debug\input.obj obj\Debug\my_complex.obj obj\Debug\output.obj obj\Debug\testfile.obj,bin\Debug\Complexe_rechnung.exe,,cw32mt.lib import32.lib,,
Output file is bin\Debug\Complexe_rechnung.exe with size 71.00 KB
Process terminated with status 0 (0 minute(s), 0 second(s))
0 error(s), 0 warning(s) (0 minute(s), 0 second(s))
 

--- End code ---

Well, that would explain a lot, if Borland is non debug compatible.

EDIT:

This happen, if i add a -g in "Settings -> compiler -> other compiler options"


--- Code: ---
-------------- Clean: Debug in Complexe_rechnung (compiler: Borland C++ Compiler (5.5, 5.82))---------------

Cleaned "Complexe_rechnung - Debug"

-------------- Build: Debug in Complexe_rechnung (compiler: Borland C++ Compiler (5.5, 5.82))---------------

bcc32.exe -q -w  -v  -g   -ID:\Programme\Borland\BCC55\Include -oobj\Debug\input.obj -c input.c
Error E2074: Value after -g or -j should be between 0 and 255 inclusive
Error E2075: Incorrect command line option: -g
Process terminated with status 1 (0 minute(s), 0 second(s))
2 error(s), 0 warning(s) (0 minute(s), 0 second(s))


--- End code ---

BlueHazzard:
http://docs.embarcadero.com/products/rad_studio/delphiAndcpp2009/HelpUpdate2/EN/html/devwin32/bcc32_xml.html


--- Quote ----g      Stop batch compilation after n warnings (Default = 255)
--- End quote ---

BlueHazzard:
why do you use bcc and not gcc?

Navigation

[0] Message Index

[#] Next page

Go to full version