How can i remove debugging information

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

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.

Quote:

---

Originally Posted by matsp

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

---

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

Quote:

---

Originally Posted by vart

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

---

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

yah i found it its on build configration and make it release without win32 debug

Quote:

---

Originally Posted by matsp

In Linux/Unix, the debug is embedded into the executable file, and using the "strip" command will remove any debug information, including symbol info.

---

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...

Quote:

---

Originally Posted by matsp

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

---

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.

Quote:

---

Originally Posted by MK27

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...

---

strip removes ALL sections from the image which are unnecessary for program execution. Not just debug info.