Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Yao Qi <qiyaoltc@gmail.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: Pedro Alves <palves@redhat.com>,
		"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: Use of mcheck during GDB development
Date: Tue, 15 Nov 2016 21:28:00 -0000	[thread overview]
Message-ID: <CAH=s-POqVZRpeb42P96QEHWBkOzBEB2Z5hw2vZnr4yZOnhJKEQ@mail.gmail.com> (raw)
In-Reply-To: <eb8546a7-ccfc-3b52-0f11-e5a78e813a8b@redhat.com>

On Tue, Nov 15, 2016 at 8:22 PM, Florian Weimer <fweimer@redhat.com> wrote:
>
> I think most people use valgrind for memory debugging.
>

FWIW, I use asan and valgrind for memory debugging in gdb work.

-- 
Yao (齐尧)


      parent reply	other threads:[~2016-11-15 21:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-15 16:00 Florian Weimer
2016-11-15 20:03 ` Pedro Alves
2016-11-15 20:22   ` Florian Weimer
2016-11-15 20:46     ` Mike Frysinger
2016-11-15 20:50     ` Pedro Alves
2016-11-15 21:58       ` Simon Marchi
2016-11-15 22:07         ` Pedro Alves
2016-11-15 22:11           ` Simon Marchi
2016-11-15 21:28     ` Yao Qi [this message]

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='CAH=s-POqVZRpeb42P96QEHWBkOzBEB2Z5hw2vZnr4yZOnhJKEQ@mail.gmail.com' \
    --to=qiyaoltc@gmail.com \
    --cc=fweimer@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@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