This is the mail archive of the gcc-help@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Stabs+ debug bloat from gcc 2.95.3 to gcc 3.3.1

From: Daniel Berlin <dberlin at dberlin dot org>
To: Philip Walford <philip_walford at yahoo dot com dot au>
Cc: gcc-help at gcc dot gnu dot org
Date: Tue, 7 Oct 2003 09:57:51 -0400
Subject: Re: Stabs+ debug bloat from gcc 2.95.3 to gcc 3.3.1
References: <1065507695.1770.245.camel@cosmo>

On Oct 7, 2003, at 2:21 AM, Philip Walford wrote:

Hi,
Our company is considering upgrading from gcc 2.95.3 to one of the 3.x
series, but we're rather concerned by the growth in debug symbols size.
Following previous discussions, I have tried the -feliminate-dwarf2-dups (still unsupported by GDB) and -gstabs+. Both of these are better than the default, but the result is still far worse than gcc 2.95.3.
Can anyone help me to understand why gcc 3.3.1 (for instance) produces
stabs+ format debug binaries that are nearly twice as large as those
produce by gcc 2.95.3?

Because 2.95.3 didn't output much debugging info, and 3.3.1 does?
It's also likely that 2.95.3 missed information that 3.3.1 doesn't.

Michael Chastain probably has gdb test results that would say one way or the other. --Dan

References:
- Stabs+ debug bloat from gcc 2.95.3 to gcc 3.3.1
  - From: Philip Walford

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]