some friend told me in networking programs when u remove debugging information exe gets smaller i wanted to ask where can i remove debugging information at msv6
and also what does makes the exe smaller or bigger.
thanks in advanced.
some friend told me in networking programs when u remove debugging information exe gets smaller i wanted to ask where can i remove debugging information at msv6
and also what does makes the exe smaller or bigger.
thanks in advanced.
In visual studio, I don't think there is much debug info in the executable itself, as it is stored in a .pdb file that is separate from the executable itself. In Linux/Unix, the debug is embedded into the executable file, and using the "strip" command will remove any debug information, including symbol info.
Compiling your code for release mode will (usually) reduce the size of the executable.
--
Mats
Compilers can produce warnings - make the compiler programmers happy: Use them!
Please don't PM me for help - and no, I don't do help over instant messengers.
It contains some slight debugging information, but not enough to radically increase the size.
I don't know how to do it in MSVC6 either, though.
Originally Posted by Adak
You have several options in Project Properties C/C++ General
Debug Info
- None - none is added
- Line Numbers Only - as it stated
- C7 Compatibale - Debug info is stored inside the exe-file (no need for pdb file)
- Progam Database - Debug info is stored in the pdb file
- Progam Database for edit enad continue - Same as above Plus additional possiblity to fix code and continue debugging without restarting the application
All problems in computer science can be solved by another level of indirection,
except for the problem of too many layers of indirection.
– David J. Wheeler
But normally, it's set to NONE for release build, as far as I remember, and C7 is not at all meaningfull unless you try to use REALLY OLD debug tools (like 10+ years old!)
--
Mats
Compilers can produce warnings - make the compiler programmers happy: Use them!
Please don't PM me for help - and no, I don't do help over instant messengers.
yah i found it its on build configration and make it release without win32 debug
I'm presuming the debug symbols are only present if you compile with "-g", and that "strip" undoes the "-g". Am I wrong?
Yep...wow look at that...
C programming resources:
GNU C Function and Macro Index -- glibc reference manual
The C Book -- nice online learner guide
Current ISO draft standard
CCAN -- new CPAN like open source library repository
3 (different) GNU debugger tutorials: #1 -- #2 -- #3
cpwiki -- our wiki on sourceforge
I like to use C7 option when I need to debug on the different comp using attach to Process feature from where I have compiled the exe - in this mode it never happens that the debug info is not found by the debugger.
All problems in computer science can be solved by another level of indirection,
except for the problem of too many layers of indirection.
– David J. Wheeler
strip removes ALL sections from the image which are unnecessary for program execution. Not just debug info.
Code://try //{ if (a) do { f( b); } while(1); else do { f(!b); } while(1); //}
