Revert of Enable extended debugging symbols to including macro expansion.

Revert of Enable extended debugging symbols to including macro expansion. (https://codereview.chromium.org/198363002/)

Reason for revert:
Linux dbg builder runs out of memory

Original issue's description:
> Adding -g3 to get macro expansion support. (Default is -g2.)
> Adding -gdwarf-4 for macro expansion support.
> 
>  * gcc 4.6 outputs DWARF-2 by default
>  * gcc 4.7 outputs DWARF-4 by default
>  * clang <3.4 outputs DWARF-3 by default
>  * clang >3.4 outputs DWARF-4 by default
> 
> From http://gcc.gnu.org/onlinedocs/gcc/Debugging-Options.html
> > -g3
> >  Level 3 includes extra information, such as all the macro
> >  definitions present in the program. Some debuggers support macro
> >  expansion when you use -g3.
> >
> > -gdwarf-4
> >  Produce debugging information in DWARF format (if that is
> >  supported). The value of version may be either 2, 3 or 4; the
> >  default version for most targets is 4.  Note that with DWARF
> >  Version 2, some ports require and always use some non-conflicting
> >  DWARF 3 extensions in the unwind tables.
> >
> >  Version 4 may require GDB 7.0 and -fvar-tracking-assignments for
> >  maximum benefit.
> 
> Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=257944
> 
> Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=280980

TBR=mark@chromium.org,mithro@mithis.com,thestig@chromium.org
NOTRY=true
NOTREECHECKS=true

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=280986

[jochen (gone - plz use gerrit), 2014-07-02 09:16:48]

Created Revert of Enable extended debugging symbols to including macro
expansion.

[commit-bot: I haz the power, 2014-07-02 09:18:06]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/jochen@chromium.org/366963002/1

[commit-bot: I haz the power, 2014-07-02 09:18:07]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2014-07-02 09:18:07]

No LGTM from a valid reviewer yet. Only full committers are accepted.
Even if an LGTM may have been provided, it was from a non-committer or
a provisional committer, _not_ a full super star committer.
See http://www.chromium.org/getting-involved/become-a-committer
Note that this has nothing to do with OWNERS files.

[jochen (gone - plz use gerrit), 2014-07-02 09:28:41]

The CQ bit was checked by jochen@chromium.org

[commit-bot: I haz the power, 2014-07-02 09:30:25]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/jochen@chromium.org/366963002/1

[commit-bot: I haz the power, 2014-07-02 09:31:40]

Change committed as 280986

[Mark Mentovai, 2014-07-02 12:24:16]

LGTM. Is this speculative or do you know that this will fix the builder?

[jochen (gone - plz use gerrit), 2014-07-02 12:41:55]

On 2014/07/02 at 12:24:16, mark wrote:
> LGTM. Is this speculative or do you know that this will fix the builder?

it fixed the builder