Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: brobecker@adacore.com, pmuldoon@redhat.com, gdb@sourceware.org
Subject: Re: py-breakpoint.c fails to compile with MinGW GCC
Date: Thu, 28 Jul 2011 16:46:00 -0000	[thread overview]
Message-ID: <m3d3gu5p62.fsf@fleche.redhat.com> (raw)
In-Reply-To: <83livie5x7.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 28 Jul	2011 19:17:08 +0300")

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


  reply	other threads:[~2011-07-28 16:46 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-28 12:07 Eli Zaretskii
2011-07-28 14:54 ` Phil Muldoon
2011-07-28 15:01   ` Tom Tromey
2011-07-28 15:19     ` Joel Brobecker
2011-07-28 15:37       ` Phil Muldoon
2011-07-28 15:44       ` Tom Tromey
2011-07-28 16:11         ` Kai Tietz
2011-07-28 16:17         ` Eli Zaretskii
2011-07-28 16:46           ` Tom Tromey [this message]
2011-07-28 17:07             ` Eli Zaretskii
2011-07-29  3:04               ` Chris Sutcliffe
2011-07-29  6:13                 ` Eli Zaretskii
2011-07-28 16:13     ` Eli Zaretskii
2011-07-28 16:25       ` Joel Brobecker
2011-07-28 16:48       ` Tom Tromey

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m3d3gu5p62.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=brobecker@adacore.com \
    --cc=eliz@gnu.org \
    --cc=gdb@sourceware.org \
    --cc=pmuldoon@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox