@billyfish

Quote:

Have you got some examples of this?

I have not built statistics but it appears to be case with most executables. Maybe not so often these days, my last experiments with OS4 executables were about five years ago (os4emu).

Quote:

One thing I would love to see in Codebench would be the ability to have separate debug and release builds with debug symbols and optimisation respectively. Of course if you're using makefiles directly, it's easy to add a BUILD= type switch

gcc -O3 source.c -o executable.db
strip -s executable.db -o executable

You get binary with debug and without debug information. Haveing separate build without optimizations is not very useful.

_________________
Amiga Developer
Amiga 500, Efika, Mac Mini and PowerBook

@Xenic

Quote:

If you are trying to squeeze every bit of memory, you could try stripping Odyssey to get another 10 MB of free memory when Odyssey is running. The downside is that you won't get as much information in Grim Reaper if Odyssey crashes.

He could but it would be pretty pointless as debug info is not loaded into memory.

_________________
BroadBlues On Blues BroadBlues On Amiga Walker Broad

@itix

Quote:

If you are lazy to not strip executables (most OS4 developers dont) you get large executables.

What is lazy about it? And unless you are building with full debug (ie -gstabs) the % increase is relatively small and doesn't affect run time memory usage.

_________________
BroadBlues On Blues BroadBlues On Amiga Walker Broad

@billyfish

Quote:

One thing I would love to see in Codebench would be the ability to have separate debug and release builds with debug symbols and optimisation respectively.

By default codebench builds the debug version and strips it to a sepaerate copy, and so does what you ask already (exept the non optimmised version whoch is useful only for certain specialist debuging senarios and should be inlficted on users.

_________________
BroadBlues On Blues BroadBlues On Amiga Walker Broad

@broadblues

Quote:

He could but it would be pretty pointless as debug info is not loaded into memory.

Well, I thought Odyssey is now faster, but that may be placebo effect.

@broadblues

Quote:

What is lazy about it? And unless you are building with full debug (ie -gstabs) the % increase is relatively small and doesn't affect run time memory usage.

Maybe lazy is wrong word but difference in executable size is huge.

@pavlor
Quote:

Well, I thought Odyssey is now faster, but that may be placebo effect.

It is placebo. Stripped executables dont run faster than unstripped.

_________________
Amiga Developer
Amiga 500, Efika, Mac Mini and PowerBook

@itix

Quote:

itix wrote: I have not built statistics but it appears to be case with most executables. Maybe not so often these days, my last experiments with OS4 executables were about five years ago (os4emu).

That might have been the case at that time, but Codebench uses the stripping technique that you suggested

Quote:

You get binary with debug and without debug information. Haveing separate build without optimizations is not very useful.

That's not true. I tend to have something like

#ifdef _DEBUG
#define CARTESIAN_COORDS_DEBUG (STM_LEVEL_INFO)
#else
#define CARTESIAN_COORDS_DEBUG (STM_LEVEL_NONE)
#endif

at the top of my source files and then have sections like

#if CARTESIAN_COORDS_DEBUG > STM_LEVEL_FINE
PrintLog (STM_LEVEL_FINE, "*** START OF PLANE VECTOR ***\n");
PrintCartesianCoords (coord1_p, GetLogOutput ());
PrintCartesianCoords (coord2_p, GetLogOutput ());
PrintCartesianCoords (coord3_p, GetLogOutput ());
PrintCartesianCoords (&first_vector, GetLogOutput ());
PrintCartesianCoords (&second_vector, GetLogOutput ());
PrintCartesianCoords (result_p, GetLogOutput ());
#endif

in the code for various debugging messages, etc. and I don't want these in the release build of my software. By having a debug build where _DEBUG is defined and a release build where it is not will give the conditional compilation of the code. The stripping technique can't do this.

cheers

billy

@billyfish

Yes you are right about debug messages. It is unfortunately something what you cant attach externally to executables :) Often it is very practical to hand out "fat" betas with debug messages so you get feedback quicker.

Last edited by itix on 27-Dec-2014 at 06:56 PM.

_________________
Amiga Developer
Amiga 500, Efika, Mac Mini and PowerBook