[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Debug as default...
From: |
Nicola Pero |
Subject: |
Re: Debug as default... |
Date: |
Wed, 20 Sep 2006 06:19:06 +0200 (CEST) |
Thanks ...
... I also noticed that according to the GNU Coding Standards, '-g' should
be used by default
when doing 'make all' ... just another reason why it looks like a good
idea to make 'make debug=yes'
the default, which I've done. :-)
I also removed the filtering of -O2 from 'make debug=yes', as it seems
that '-g -O2' is a good
set of flags ... I think the -O2 causes GCC to do some flow analysis that
causes it to generate
better warnings ...
Hmmm ... maybe we should be using '-g -O' rather than '-g -O2'. The doc
says:
-O1: "Some transformations that preserve execution ordering. Debuggability
of the generated code is hardly affected. User variables should not
disappear and function inlining is not done."
-O2: "More aggressive transformations that may affect execution ordering
and usually provide faster code. Debuggability may be somewhat compromised
by disappearing user variables and function bodies."
Anyway, let me know if '-g -O2' causes problems, I presume if the '-O2'
seriously confuse the
debugger let me know and we can revert that change, or maybe use '-g -O' ?
Thanks
-----Original Message-----
From: "Gregory John Casamento" <address@hidden>
Sent: Tuesday, September 12, 2006 2:41 pm
To: "Riccardo" <address@hidden>
Cc: "GNUstep Developers" <address@hidden>
Subject: Re: Debug as default...
Riccardo,
Debug symbols don't take up extra memory, since they are not loaded by the
runtime linker.
Later, GJC
--Gregory Casamento
----- Original Message ----
From: Riccardo <address@hidden>
To: Gregory John Casamento <address@hidden>
Cc: GNUstep Developers <address@hidden>
Sent: Monday, September 11, 2006 5:43:21 PM
Subject: Re: Debug as default...
Hey,
On Sunday, September 10, 2006, at 07:40 AM, Gregory John Casamento wrote:
> I'm mentioning this again in order to start a discussion on the
> pros/cons of doing this.
since I find that lately gnustep is sluggish enough by itself and swaps
wildly while loading... I'd vote against that.
A reasonable setup would be to have it on for the svn version, but
disabled in the release tarballs?
Or should be more seriously speak about stable and unstable releases?
O just enable -g with "make debug=yes" it makes more sense to me than
"strip=yes"
-R
_______________________________________________
Gnustep-dev mailing list
address@hidden
http://lists.gnu.org/mailman/listinfo/gnustep-dev
_______________________________________________
Gnustep-dev mailing list
address@hidden
http://lists.gnu.org/mailman/listinfo/gnustep-dev