This is the mail archive of the gdb@sourceware.org mailing list for the GDB 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: py-breakpoint.c fails to compile with MinGW GCC

From: Tom Tromey <tromey at redhat dot com>
To: Eli Zaretskii <eliz at gnu dot org>
Cc: brobecker at adacore dot com, pmuldoon at redhat dot com, gdb at sourceware dot org
Date: Thu, 28 Jul 2011 10:46:13 -0600
Subject: Re: py-breakpoint.c fails to compile with MinGW GCC
References: <E1QmPMV-0007CR-Tf@fencepost.gnu.org> <m3vcumzc9x.fsf@redhat.com> <m3hb6678l0.fsf@fleche.redhat.com> <20110728151915.GU1988@adacore.com> <m34o2676m8.fsf@fleche.redhat.com> <83livie5x7.fsf@gnu.org>

Eli> I will probably upgrade when 4.7 is released, because I understand it
Eli> will be more debug-friendly.

Is there something specific in 4.7 you are waiting for?  4.6 is probably
good enough -- it has the biggest improvement (VTA -- first in 4.5) plus
a few more -- but I don't know of anything so major that would advise
skipping 4.6.

In practice I build gdb with -O0 when I want to debug.  Occasionally I
just rebuild a single .o this way.  VTA is good, but when debugging I
care about 100% visibility into the source and nearly zero about
performance.

Tom

Follow-Ups:
- Re: py-breakpoint.c fails to compile with MinGW GCC
  - From: Eli Zaretskii

References:
- py-breakpoint.c fails to compile with MinGW GCC
  - From: Eli Zaretskii
- Re: py-breakpoint.c fails to compile with MinGW GCC
  - From: Phil Muldoon
- Re: py-breakpoint.c fails to compile with MinGW GCC
  - From: Tom Tromey
- Re: py-breakpoint.c fails to compile with MinGW GCC
  - From: Joel Brobecker
- Re: py-breakpoint.c fails to compile with MinGW GCC
  - From: Tom Tromey
- Re: py-breakpoint.c fails to compile with MinGW GCC
  - From: Eli Zaretskii

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