search for: vgdb

...942..070fd6d 100644 --- a/m4/guestfs_progs.m4 +++ b/m4/guestfs_progs.m4 @@ -125,7 +125,7 @@ dnl Check for valgrind AC_CHECK_PROG([VALGRIND],[valgrind],[valgrind],[no]) AS_IF([test "x$VALGRIND" != "xno"],[ # Substitute the whole valgrind command. - VG='$(VALGRIND) --vgdb=no --log-file=$(abs_top_builddir)/tmp/valgrind-%q{T}-%p.log --leak-check=full --error-exitcode=119 --suppressions=$(abs_top_srcdir)/valgrind-suppressions' + VG='$(VALGRIND) --vgdb=no --log-file=$(abs_top_builddir)/tmp/valgrind-%q{T}-%p.log --leak-check=full --error-exitcode=119 --suppres...

...ry to reproduce, but I'd think someone else would have already noticed/complained if it was that badly broken.. > > What's your doveconf -n? Also can you try running via valgrind to see what it logs before the crash? : > > service lmtp { > executable = /usr/bin/valgrind --vgdb=no -q /usr/libexec/dovecot/lmtp # or whatever the lmtp path really is > } > As this is not easily reproducible with a common lmtp proxying configuration, we would be interested in the doveconf -n output from all involved nodes (proxy, director, backend). Did you have a chance to try the val...

...64-linux --3135-- object doesn't have a symbol table --3135-- object doesn't have a dynamic symbol table --3135-- Scheduler: using generic scheduler lock implementation. --3135-- Reading suppressions file: /usr/lib64/valgrind/default.supp ==3135== embedded gdbserver: reading from /tmp/vgdb-pipe-from-vgdb-to-3135-by-root-on-mems ==3135== embedded gdbserver: writing to /tmp/vgdb-pipe-to-vgdb-from-3135-by-root-on-mems ==3135== embedded gdbserver: shared mem /tmp/vgdb-pipe-shared-mem-vgdb-3135-by-root-on-mems ==3135== ==3135== TO CONTROL THIS PROCESS USING vgdb (which you probably ==3135...

http://bugzilla.netfilter.org/show_bug.cgi?id=741 Summary: ULOGD segfaults on init Product: ulogd Version: SVN (please provide timestamp) Platform: i386 OS/Version: other Status: NEW Severity: blocker Priority: P5 Component: ulogd_MYSQL AssignedTo: netfilter-buglog at lists.netfilter.org

...eone else would have already noticed/complained if it was that badly broken.. >>> >>> What's your doveconf -n? Also can you try running via valgrind to see what it logs before the crash? : >>> >>> service lmtp { >>> executable = /usr/bin/valgrind --vgdb=no -q /usr/libexec/dovecot/lmtp # or whatever the lmtp path really is >>> } >>> >> As this is not easily reproducible with a common lmtp proxying >> configuration, we would be interested in the doveconf -n output from >> all involved nodes (proxy, director, backe...

WINS nsswitch module -------------------- The WINS nsswitch module has been rewritten to address memory issues and to simplify the code. The module now uses libwbclient to do WINS queries. This means that winbind needs to be running in order to resolve WINS names using the nss_wins module. This does not affect smbd. my problem: old versions >> ping google.com >> PING google.com

I haven't done any R memory debugging lately, but https://www.mail-archive.com/rcpp-devel at lists.r-forge.r-project.org/msg10289.html shows how I used to have gdb break where valgrind finds a problem so you could examine the details. Also, running your code after running gctorture(TRUE) can help track down memory problems. -Bill On Wed, Feb 7, 2024 at 12:03?PM Therneau, Terry M., Ph.D.

...try to reproduce, but I'd think someone else would have already noticed/complained if it was that badly broken.. > > What's your doveconf -n? Also can you try running via valgrind to see what it logs before the crash? : > > service lmtp { > executable = /usr/bin/valgrind --vgdb=no -q /usr/libexec/dovecot/lmtp # or whatever the lmtp path really is > } I don't really know why this started happening with you now, but it should be fixed by https://github.com/dovecot/core/commit/16b5dc27e7db42849510403d37e3629aba14de21 <https://github.com/dovecot/core/commit/16b5dc2...

Fixes for various issues found while implementing my nbd forwarder plugin. I'm okay if you choose to take some but not others; the most important one is patch 3 which fixes a protocol violation that makes it impossible for a client to try and recover from EIO failures over a partially-flaky source block device. Eric Blake (3): maint: Add emacs hint file maint: Add NBDKIT_GDB support to

On 2017-05-02 09:35, Aki Tuomi wrote: > On 2017-05-02 10:20, Tom Sommer wrote: >> On 2017-05-01 19:26, Aki Tuomi wrote: >>>> On May 1, 2017 at 8:21 PM Tom Sommer <mail at tomsommer.dk> wrote: >>>> >>>> >>>> I just upgraded our Director to 2.2.29.1 from 2.2.26, and now my >>>> dmesg >>>> and /var/log/messages

...ake ./configure error out hard if $MAKE is not GNU Make, rather than risking someone getting 80% though a build on BSD make and then choking when it gets here? > +++ b/wrapper.c > @@ -130,8 +130,9 @@ main (int argc, char *argv[]) > passthru (VALGRIND); > passthru ("--vgdb=no"); > passthru ("--leak-check=full"); > + passthru ("--show-leak-kinds=all"); I could understand this if we were implementing a library and wanted to make it easier for some other user to call our library shutdown to reclaim all memory that we otherwise...

No. Compiling entirely from -git source (on one system) and a Gentoo ebuild on another two. Reuben On 12/10/2017 10:38 PM, Aki Tuomi wrote: > Are you using the xi packages? If yes, can you please send me one fresh core? > > Aki > >> On October 12, 2017 at 8:43 AM Aki Tuomi <aki.tuomi at dovecot.fi> wrote: >> >> >> We'll take a look >>

....in | 2 ++ 1 file changed, 2 insertions(+) diff --git a/nbdkit.in b/nbdkit.in index 167d512..878a6bd 100644 --- a/nbdkit.in +++ b/nbdkit.in @@ -103,6 +103,8 @@ fi # the program under valgrind. This is used by the tests. if [ "$NBDKIT_VALGRIND" ]; then valgrind="@VALGRIND@ --vgdb=no --leak-check=full --error-exitcode=119 --suppressions=$s/valgrind-suppressions --trace-children=no --child-silent-after-fork=yes --run-libc-freeres=no" +else + unset valgrind fi # Run the final command. -- 2.13.2 Rich. -- Richard Jones, Virtualization Group, Red Hat http://peopl...

...ave MAKEFLAGS=j<N> set in my environment and BSD make gives an error about an unknown parameter which completely breaks ./configure too ... > >+++ b/wrapper.c > >@@ -130,8 +130,9 @@ main (int argc, char *argv[]) > > passthru (VALGRIND); > > passthru ("--vgdb=no"); > > passthru ("--leak-check=full"); > >+ passthru ("--show-leak-kinds=all"); > > I could understand this if we were implementing a library and wanted > to make it easier for some other user to call our library shutdown > to reclaim all...

...nt backends)? We'll try to reproduce, but I'd think someone else would have already noticed/complained if it was that badly broken.. What's your doveconf -n? Also can you try running via valgrind to see what it logs before the crash? : service lmtp { executable = /usr/bin/valgrind --vgdb=no -q /usr/libexec/dovecot/lmtp # or whatever the lmtp path really is }

...ne else would >> have already noticed/complained if it was that badly broken.. >> >> What's your doveconf -n? Also can you try running via valgrind to see >> what it logs before the crash? : >> >> service lmtp { >> executable = /usr/bin/valgrind --vgdb=no -q >> /usr/libexec/dovecot/lmtp # or whatever the lmtp path really is >> } >> > As this is not easily reproducible with a common lmtp proxying > configuration, we would be interested in the doveconf -n output from > all involved nodes (proxy, director, backend). >...

...that badly >>>> broken.. >>>> >>>> What's your doveconf -n? Also can you try running via valgrind to >>>> see what it logs before the crash? : >>>> >>>> service lmtp { >>>> executable = /usr/bin/valgrind --vgdb=no -q >>>> /usr/libexec/dovecot/lmtp # or whatever the lmtp path really is >>>> } >>>> >>> As this is not easily reproducible with a common lmtp proxying >>> configuration, we would be interested in the doveconf -n output from >>> all...

Could you try running with valgrind and show the valgrind output in Dovecot's error logs? : service doveadm { executable = /usr/bin/valgrind -q --vgdb=no /usr/libexec/dovecot/doveadm-server } > On 12 Oct 2017, at 23.10, Reuben Farrelly <reuben-dovecot at reub.net> wrote: > > No. Compiling entirely from -git source (on one system) and a Gentoo ebuild on another two. > > Reuben > > On 12/10/2017 10:38 PM, Aki Tuomi w...

Currently we are unable to properly run guestfsd (the daemon) under valgrind. Attempts to run valgrind inside the appliance have not been successful (see patch 1/7). However we desperately need better valgrind coverage of the daemon, particularly because it is doing a lot of complex parsing of program output. This has been a problem for a long time. A better way to attack this problem is to

In v2: - Kernel command line parsing now moved to the appliance. - In the captive daemon test, the daemon cleanly shuts down on exit. - Add another btrfs test. Rich.