similar to: [patch] let valgrind run on login process with GDB=1

Hi, with a low soft limit on file descriptors, dovecot 2.2.15 warns on startup: Warning: fd limit (ulimit -n) is lower than required under max. load (256 < 1000), because of default_client_limit It could try increasing the limit first, and only report the warning if that fails. I'm attaching a patch that does just this. Without the patch, the soft fd limit is kept at whatever it

Hi, all, The mail_filter plugin allows you to pass messages through an external script/command on the way into and out of the Maildir/mbox/etc mail store. With the recent/new version of the plugin, this seems to work correctly. However, my mail-filter script (for filtering messages on the way from the mail store through the IMAP process to a remote client) needs some extra info from the IMAP

Hi. Does someone make update for `Multiple IP(or Host) listen in dovecot.conf'? I made trivial patch so. But this patch doesn't solve `Support listening in multiple sockets' in TODO. It appends only the capability as multiple listen in dovecot.conf. So, `login_processes_count' becomes ambiguous. In CASE1, login_processes_count = 2, forked imap-login processes are 8. -- samples

On 22 Jan 2015, at 14:01, Lauri Tirkkonen <ltirkkon at niksula.hut.fi> wrote: > > Hi, with a low soft limit on file descriptors, dovecot 2.2.15 warns on > startup: > > Warning: fd limit (ulimit -n) is lower than required under max. load > (256 < 1000), because of default_client_limit > > It could try increasing the limit first, and only report the warning

As an update to the nouveau development community, the downstream fork of Valgrind with a mmap tracing tool ("mmt") we maintain has been rebased against the latest upstream release of Valgrind, v3.16.1 Code branch: https://github.com/envytools/valgrind/tree/mmt-3.16.1 Features of upstream Valgrind 3.16.x: https://www.valgrind.org/docs/manual/dist.news.html In selected highlights, the

On Sun, Jul 01, 2018 at 12:50:46PM +0100, Richard W.M. Jones wrote: > diff --git a/src/Makefile.am b/src/Makefile.am > index 7ead75c..915efe4 100644 > --- a/src/Makefile.am > +++ b/src/Makefile.am > @@ -63,7 +63,8 @@ nbdkit_CPPFLAGS = \ > nbdkit_CFLAGS = \ > -pthread \ > $(WARNINGS_CFLAGS) \ > - $(GNUTLS_CFLAGS) > + $(GNUTLS_CFLAGS) \ > + $(VALGRIND_CFLAGS)

Dear all, I'm trying to debug my R package with valgrind, but I cannot get past the point where I load make the data, as valgrind crashes when trying to extract a single time series object of a multivariate mts object. I'm using R 2.15.0 with platform x86_64-redhat-linux-gnu (64-bit). The valgrind.R contains code data(Seatbelts) y<-Seatbelts[,"VanKilled"] And I run

R CMD check --use-valgrind <packagename> used to run valgrind on the tests in the tests directory of the package. But it seems to have stopped. R-2.9.1 doesn't -- at least on my box -- and neither does R-2.10.0 (devel). I am not sure when this stopped. I think 2.8.x did this. The only old R I have around is 2.6.0 and it certainly does. R CMD check --help for 2.9.1 says (among other

When valgrinding plugins, the following sequence can happen: plugin_free -> dlclose -> unloads the plugin and symbol table exit -> valgrind prints failures (the same applies to filters). When valgrind is printing the failures, it looks up the addresses in the symbol table, but that has been unloaded already so all you see are "???", resulting in useless

I had to add several suppressions because Python leaks memory by design, and also increase the max depth of valgrind stack traces because Python stack traces are very deep. Note that to do proper valgrinding of Python itself we would need to specially recompile Python: https://svn.python.org/projects/python/trunk/Misc/README.valgrind --- tests/test-lang-plugins.c | 3 +-

List, Anybody have a script around that will do this? We have to run valgrind and asterisk to help troubleshoot a bug in the tracker. Since we do not know how to reproduce the error, we'd like to run them from an init.d script (simalar to safe_asterisk), email on crash, and restart asterisk. Ideas? Thanks, PB

Hi, I am trying to debug a package which I helped to develop since we were notified by CRAN that our package randomly fails to run its examples. Hence, I reinstalled R with "with-valgrind-instrumentation=2" and installed our package with MAKEFLAGS="CFLAGS='-O0 -g3' CXXFLAGS='-O0 -g3'" R CMD INSTALL --build hsmm Then, I ran the examples of our package with R

NUT developers, just thought I'd share some notes and ideas on using valgrind against the NUT USB drivers on Linux. Stepping back a bit, I wanted to make sure that the tripplite_usb driver* wasn't using any uninitialized memory, or leaking memory over time. valgrind (specifically, the memcheck tool) runs the code in a special dynamic translator that checks every memory access to see if

--- extratests/Makefile.am | 8 ++++++-- 1 files changed, 6 insertions(+), 2 deletions(-) diff --git a/extratests/Makefile.am b/extratests/Makefile.am index bf6b3f9..519d0b9 100644 --- a/extratests/Makefile.am +++ b/extratests/Makefile.am @@ -52,12 +52,16 @@ EXTRA_DIST = suppressions +VG_FIFO=$(abs_builddir)/valgrind.fifo +VG_LOG=$(abs_builddir)/valgrind.log VG = valgrind \ -

Hi, I've made a simple patch to allow running LLVM's test suite under valgrind. By default it doesn't do any memory leak checking because valgrind reports problems in most tests.. To run the tests with valgrind one has to run 'cd test && make VG=1', similar with what we have with clang. So is this patch ok and/or desirable? Regards, Nuno P.S.: Warning: it takes a

Hi, Lit utility has valgrind tests already implemented, that are called using --vg parameter. What does "LLVM style valgrind" mean in lit's TODO? What is LLVM style? Thanks, Sergey

Hi All Though, I have used clang which is great. I am dumb in LLVM design. Will somebody be kind enough to answer Will LLVM be suitable for developing valgrind like tools? Regards --Dev -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130107/84a92ae4/attachment.html>

Hi All Will LLVM be suitable for developing valgrind like tools --Regards --Dev -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130107/ab5ef642/attachment.html>

> Will LLVM be suitable for developing valgrind like tools It is already used by several such tools, eg ASAN, klee. Ciao, Duncan.

http://developer.kde.org/~sewardj/ Valgrind is a GPL'd tool to help you find memory-management problems in your programs. When a program is run under Valgrind's supervision, all reads and writes of memory are checked, and calls to malloc/new/free/delete are intercepted. As a result, Valgrind can detect problems such as: * Use of uninitialised memory * Reading/writing memory after