This is the mail archive of the gcc@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: Unifying the GCC Debugging Interface

From: Diego Novillo <dnovillo at google dot com>
To: Andrew Pinski <pinskia at gmail dot com>
Cc: Lawrence Crowl <crowl at googlers dot com>, "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>
Date: Fri, 16 Nov 2012 08:10:13 -0500
Subject: Re: Unifying the GCC Debugging Interface
References: <CAGqM8fZ+LTC9tK_z=JXruwdmJyeWVMW6MA2oQYxYRh54zpHvFA@mail.gmail.com> <CA+=Sn1mcE3ejawLUmODaWkUkyOH+mbfthp7o_-8d5C0tOu80rA@mail.gmail.com>

On Wed, Nov 14, 2012 at 8:48 PM, Andrew Pinski <pinskia@gmail.com> wrote:

> Here is my proposal though I don't have time to work on it.  Make some
> python scripts which do the basic function of the debug_* functions.

No.  Debug traces and -fdump-* support.

Python pretty printers for gdb would be great, of course.  They are
just not a replacement for having our own dump facilities in the
compiler.

Diego.

References:
- Unifying the GCC Debugging Interface
  - From: Lawrence Crowl
- Re: Unifying the GCC Debugging Interface
  - From: Andrew Pinski

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