From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Aravinda <aravindakidambi@gmail.com>
Cc: Stan Shebs <stan@codesourcery.com>,
ppluzhnikov@google.com, dave.korn.cygwin@googlemail.com,
gdb@sourceware.org
Subject: Re: GDB library to insert and delete watchpoints
Date: Fri, 04 Dec 2009 17:11:00 -0000 [thread overview]
Message-ID: <20091204171129.GA13936@host0.dyn.jankratochvil.net> (raw)
In-Reply-To: <26eb53620912040820y3340ad2fw78bf770754b26c4c@mail.gmail.com>
On Fri, 04 Dec 2009 17:20:57 +0100, Aravinda wrote:
> that I want to be safe from buffer overruns all the time,
FYI there is `gcc -fmudflap -lmudflap'.
Regards,
Jan
next prev parent reply other threads:[~2009-12-04 17:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <26eb53620911301516x68ccc0edkf64ba2951c8ce3a3@mail.gmail.com>
[not found] ` <26eb53620911301518y13e64bc0g95c6fe3c7b18b0c@mail.gmail.com>
2009-12-01 5:44 ` Paul Pluzhnikov
2009-12-01 18:08 ` Dave Korn
2009-12-01 21:14 ` Jan Kratochvil
2009-12-04 8:51 ` Stan Shebs
2009-12-04 16:21 ` Aravinda
2009-12-04 17:11 ` Jan Kratochvil [this message]
2009-12-07 21:30 ` Aravinda
2009-12-04 16:38 ` Joel Brobecker
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=20091204171129.GA13936@host0.dyn.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=aravindakidambi@gmail.com \
--cc=dave.korn.cygwin@googlemail.com \
--cc=gdb@sourceware.org \
--cc=ppluzhnikov@google.com \
--cc=stan@codesourcery.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