From: Neil Jerram <neil@ossau.uklinux.net>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-user@gnu.org
Subject: Re: Valgrind warnings with -1.8.6
Date: Sun, 12 Apr 2009 08:11:35 +0100 [thread overview]
Message-ID: <8763hal520.fsf@arudy.ossau.uklinux.net> (raw)
In-Reply-To: <877i1vy4u5.fsf@gnu.org> ("Ludovic Courtès"'s message of "Wed\, 08 Apr 2009 09\:36\:34 +0200")
ludo@gnu.org (Ludovic Courtès) writes:
> Hello,
>
> Neil Jerram <neil@ossau.uklinux.net> writes:
>
>> That is fundamentally true; however, we have recently addressed some
>> genuine Valgrind warnings in the 1.8.x development branch.
>
> These were Helgrind warnings, not Memcheck warnings, right?
Yes, good point!
Neil
next prev parent reply other threads:[~2009-04-12 7:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-06 15:05 Valgrind warnings with -1.8.6 Andrew Gaylard
2009-04-07 10:40 ` Andrew Gaylard
2009-04-07 19:47 ` Andreas Rottmann
2009-04-07 21:25 ` Neil Jerram
2009-04-08 7:36 ` Ludovic Courtès
2009-04-08 13:38 ` Paul Emsley
2009-04-12 7:11 ` Neil Jerram [this message]
2009-04-30 9:12 ` Andrew Gaylard
2009-04-30 21:09 ` Ludovic Courtès
2009-05-01 10:13 ` Andy Wingo
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8763hal520.fsf@arudy.ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--cc=guile-user@gnu.org \
--cc=ludo@gnu.org \
/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).