From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-37747-listarch-gdb=sources.redhat.com@sourceware.org>
Received: (qmail 13357 invoked by alias); 30 Jul 2010 19:53:07 -0000
Received: (qmail 13348 invoked by uid 22791); 30 Jul 2010 19:53:07 -0000
X-SWARE-Spam-Status: No, hits=-1.6 required=5.0	tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM
X-Spam-Check-By: sourceware.org
Received: from mail-gx0-f169.google.com (HELO mail-gx0-f169.google.com) (209.85.161.169)    by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 30 Jul 2010 19:53:02 +0000
Received: by gxk4 with SMTP id 4so995542gxk.0        for <gdb@sourceware.org>; Fri, 30 Jul 2010 12:53:01 -0700 (PDT)
Received: by 10.151.115.8 with SMTP id s8mr3721586ybm.437.1280519580502; Fri, 	30 Jul 2010 12:53:00 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.231.207.14 with HTTP; Fri, 30 Jul 2010 12:52:40 -0700 (PDT)
In-Reply-To: <m3k4oc6ayc.fsf@fleche.redhat.com>
References: <4C4EFC98.7080105@wh2.tu-dresden.de> <m3k4oc6ayc.fsf@fleche.redhat.com>
From: =?UTF-8?B?UGV0ciBIbHV6w61u?= <petr.hluzin@gmail.com>
Date: Fri, 30 Jul 2010 19:53:00 -0000
Message-ID: <AANLkTimUW1YazEcA1D-LQDD2fEdTQT6Dw0t1CniOOeHx@mail.gmail.com>
Subject: Re: Crashing gdb with python-prettyprinting
To: Tom Tromey <tromey@redhat.com>
Cc: Joachim Protze <joachim.protze@wh2.tu-dresden.de>, gdb@sourceware.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-IsSubscribed: yes
Mailing-List: contact gdb-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb.sourceware.org>
List-Subscribe: <mailto:gdb-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb/>
List-Post: <mailto:gdb@sourceware.org>
List-Help: <mailto:gdb-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-owner@sourceware.org
X-SW-Source: 2010-07/txt/msg00129.txt.bz2

On 30 July 2010 21:12, Tom Tromey <tromey@redhat.com> wrote:
> Joachim> I also tried to run gdb with duma to find the memory failure,
> Joachim> where the frame_info is overwritten, but with running duma each
> Joachim> step and each function call of gdb gets damn slow.
>
> I don't know what duma is. =C2=A0I tend to use valgrind for this sort of
> thing. =C2=A0That is slower than running native, but for most things, not
> unbearably so.

FYI: DUMA is a GLP library to detect buffer overruns and under-runs in
C and C++ programs. http://duma.sourceforge.net/

Basically it works the same way as ElectricFence (guard page after
each allocation).
I am sad to hear it is slow.

--=20
Petr Hluzin