From: David Bremner <david@tethera.net>
To: Tomi Ollila <tomi.ollila@iki.fi>, notmuch@notmuchmail.org
Subject: Re: [PATCH] lib: add talloc reference from string map iterator to map
Date: Sat, 24 Sep 2016 08:16:44 -0300 [thread overview]
Message-ID: <87mvixcztv.fsf@zancas.localnet> (raw)
In-Reply-To: <m2intlzkpj.fsf@guru.guru-group.fi>
Tomi Ollila <tomi.ollila@iki.fi> writes:
>
> I tried to run this under valgrind ( ./T610-message-property.sh --valgrind )
> but got so noisy output that I could not resolve anything definite
> from it.
Hmm. On a related topic, --valgrind seems broken here:
╭─ zancas:software/upstream/notmuch/test
╰─ (git)-[master]-% ./T610-message-property.sh --val
./test-lib.sh:[:18: unknown condition: -lt
./test-lib.sh:27: command not found: shopt
test-lib: Testing message property API
cc1: error: unrecognised debug output level ' -O0'
All the tests fail because none of the binaries get built.
Same results if I run from bash instead of my normal zsh.
> Also /T600-named-queries.sh --val printed noisy output -- but perhaps
> the noise difference (less there) can inform something.
I ran
% ./T610-message-property --debug
% cd tmp.T610-message-property
% LD_LIBRARY_PATH=../../lib valgrind ./test6 `pwd`/mail
>
> Anyway, this seems to fix a bug that might affect someone, and at least
> the situation is better with this so this should be pushed soon...
>
> Btw: does 'Debian stable' refer to Debian 8.6(+) -- just for the record
> anyone reading this message years from now :D
Yes, thanks for reminding me to upgrade ;). I tested and the failure is
there with 8.6
d
next prev parent reply other threads:[~2016-09-24 11:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-23 9:33 [PATCH] lib: add talloc reference from string map iterator to map David Bremner
2016-09-24 9:54 ` Tomi Ollila
2016-09-24 11:16 ` David Bremner [this message]
2016-09-24 11:43 ` Tomi Ollila
2016-09-24 13:18 ` David Bremner
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://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mvixcztv.fsf@zancas.localnet \
--to=david@tethera.net \
--cc=notmuch@notmuchmail.org \
--cc=tomi.ollila@iki.fi \
/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.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
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).