From: "Petr Hluzín" <petr.hluzin@gmail.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Joachim Protze <joachim.protze@wh2.tu-dresden.de>, gdb@sourceware.org
Subject: Re: Crashing gdb with python-prettyprinting
Date: Fri, 30 Jul 2010 19:53:00 -0000 [thread overview]
Message-ID: <AANLkTimUW1YazEcA1D-LQDD2fEdTQT6Dw0t1CniOOeHx@mail.gmail.com> (raw)
In-Reply-To: <m3k4oc6ayc.fsf@fleche.redhat.com>
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. I tend to use valgrind for this sort of
> thing. That 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.
--
Petr Hluzin
next prev parent reply other threads:[~2010-07-30 19:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-27 15:35 Joachim Protze
2010-07-30 19:12 ` Tom Tromey
2010-07-30 19:53 ` Petr Hluzín [this message]
2010-08-09 12:19 ` Joachim Protze
2010-08-10 10:57 ` Joachim Protze
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=AANLkTimUW1YazEcA1D-LQDD2fEdTQT6Dw0t1CniOOeHx@mail.gmail.com \
--to=petr.hluzin@gmail.com \
--cc=gdb@sourceware.org \
--cc=joachim.protze@wh2.tu-dresden.de \
--cc=tromey@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).