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: Gabriel Dos Reis <gdr at integrable-solutions dot net>
To: Richard Biener <richard dot guenther 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: Sun, 25 Nov 2012 13:51:58 -0600
Subject: Re: Unifying the GCC Debugging Interface
References: <CAGqM8fZ+LTC9tK_z=JXruwdmJyeWVMW6MA2oQYxYRh54zpHvFA@mail.gmail.com> <CAFiYyc2gVKcdKfCd0n=46cVA0mn8K0QMSoJ_aUeViW_E844Z5w@mail.gmail.com>

On Sun, Nov 25, 2012 at 7:45 AM, Richard Biener
<richard.guenther@gmail.com> wrote:

> Just to add another case which seems to be not covered in the thread.
> When dumping from inside a gdb session in many cases I cut&paste
> addresses literally.  For overloading to work I'd need to write casts
> in front of the inferior call argument.  That sounds ugly - so at least
> keep the old interfaces as well.  Or rather for debugging purposes
> provide python helpers rather than new inferior overloads.

this means that we need an improvement from GDB.  This
is not useful only to the small GCC community.  It is very useful to
the wider GDB/C++ user community.

-- Gaby

Follow-Ups:
- Re: Unifying the GCC Debugging Interface
  - From: Tom Tromey

References:
- Unifying the GCC Debugging Interface
  - From: Lawrence Crowl
- Re: Unifying the GCC Debugging Interface
  - From: Richard Biener

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