similar to: RE: RE: winbindd panic daemon dies

Displaying 20 results from an estimated 100 matches similar to: "RE: RE: winbindd panic daemon dies"

2020 Apr 09
5
[Bug 1418] New: segfaults when running nft --file foo.nft --echo
https://bugzilla.netfilter.org/show_bug.cgi?id=1418 Bug ID: 1418 Summary: segfaults when running nft --file foo.nft --echo Product: nftables Version: unspecified Hardware: x86_64 OS: All Status: NEW Severity: enhancement Priority: P5 Component: nft Assignee: pablo at
2013 Feb 20
0
[LLVMdev] LLVM Interpreter & QSort
Hi, I am trying to run an LLVM analysis on a C++ program that calls qsort(), using the LLVM interpreter (lli --force-interpreter). The code is the qsort_large.c file in the MiBench benchmark suite. If I comment the qsort() call, the execution works fine. If I uncomment the qsort() call, I run into a segmentation fault error as follows: 0  lli             0x0000000000d35c6f 1  lli        
2013 Feb 20
0
[LLVMdev] LLVM Interpreter & Qsort
Hi, I am trying to run an LLVM analysis on a C++ program that calls qsort(), using the LLVM interpreter (lli --force-interpreter). The code is the qsort_large.c file in the MiBench benchmark suite. If I comment the qsort() call, the execution works fine. If I uncomment the qsort() call, I run into a segmentation fault error as follows: 0 lli 0x0000000000d35c6f 1 lli
2007 Jul 13
0
KWD crashes when opening OOo
Hello, KWD crashes almost regularly when trying to start OpenOffice.org. I've attached two output files from valgrind to this e-mail (as suggested by David Reveman in another mail 11.7): Use something like: valgrind --tool=memcheck kde-window-decorator .... I'm using Trevino's git version of Compiz in up-to-date Kubuntu Feisty system. Compiz version is
2005 Jan 31
0
Strange sip address?
Hi all, I am struggling to make my asterisk server work. The problem is I can not place a call from a phone outside, but I can call out from a phone in the local network where the asterisk server sits. I turn the debug on, and the log are shown below. I can see "REGISTER" method is OK. ( SIP/2.0 200 OK) But Later, in the "INVITE" method, the SIP addresses become
2018 Dec 04
3
Dovecot 2.3.4 crash
A full example with dovecot debug symbols activated (note since I have activate valgrind, no more segfault it?s normal I presume ): Dec 4 12:09:40 dovecot: auth-worker: Error: ==3071== Invalid read of size 8 Dec 4 12:09:40 dovecot: auth-worker: Error: ==3053== Invalid read of size 8 Dec 4 12:09:40 dovecot: auth-worker: Error: ==3057== Invalid read of size 8 Dec 4 12:09:40 dovecot:
2019 Feb 27
0
Intermittent crashes with inset `[<-` command
On an azure centos VM, I can reproduce this bug which reports either: *** caught segfault *** address 0x70000006a, cause 'memory not mapped' (crash) Or incompatible types (from builtin to integer) in subassignment type fix (no crash) Like Gabriel, I could not reproduce the bug on a mac laptop. Both R versions 3.5.1. Travers On Wed, Feb 27, 2019 at 9:08 AM William Dunlap via R-devel
2018 Dec 04
0
Dovecot 2.3.4 crash
Hi ! Yes it happens every 2 to 5 minutes so no problem in reproducing. I made the change with valgrind, I have now this in my log : Dec 4 12:00:27 xxxxx dovecot: auth-worker: Error: ==2436== Invalid read of size 8 Dec 4 12:00:27 xxxxx dovecot: auth-worker: Error: ==2393== Invalid read of size 8 Dec 4 12:00:27 xxxxx dovecot: auth-worker: Error: ==2476== Invalid read of size 8 Dec 4 12:00:27
2007 Jun 13
0
Reported invalid memory references
While testing for leaks in my own code I noticed some reported memory problems from valgrind, invoked with $ R --vanilla -d "valgrind --leak-check=full" This is on Debian GNU/Linux (testing aka lenny) with a 2.6 kernel, R package version 2.4.1-2. I was running in an emacs shell. The immediate source of all the problems before I get to the prompt is the system dynamic loader
2013 May 30
0
[LLVMdev] unexpectedly loop hanging
Hi Alexandru, > /*==5134== Invalid write of size 4 > ==5134== at 0x4039280: (anonymous > namespace)::Hello::runOnModule(llvm::Module&) (in > /home/alex/llvm/Release+Asserts/lib/Hello.so) > ==5134== by 0x8E33DE3: llvm::MPPassManager::runOnModule(llvm::Module&) (in > /home/alex/llvm/Release+Asserts/bin/opt) > ==5134== by 0x8E3726F:
2009 May 26
5
errors in valgrind
Hay! Has anyone come across these errors using valgrind for the oggenc tool or the encoder_example.c: ==13108== Invalid read of size 4 ==13108== at 0x4155734: _vp_offset_and_mix (in /usr/local/lib/libvorbis.so.0.4.1) ==13108==
2013 May 30
0
[LLVMdev] unexpectedly loop hanging
Hi Alexandru, if these are LLVM Makefiles, then I suggest you configure and build LLVM with the options: --disable-optimized --enable-assertions This will make debugging much easier. It enables debug info too, which you can also turn on directly by configuring with --enable-debug-symbols. Ciao, Duncan. On 30/05/13 14:21, Alexandru Ionut Diaconescu wrote: > Hello Duncan, > > Thank
2012 Feb 03
0
[LLVMdev] Issues with the llvm.stackrestore intrinsic - now LoopRotation handling of alloca
Hi, I've tracked the first problem (mentioned in my previous email, quoted below) down further, ending up in the handling of alloca in LoopRotation.cpp (from trunk): // If the instruction's operands are invariant and it doesn't read or write // memory, then it is safe to hoist. Doing this doesn't change the order of // execution in the preheader, but does
2012 Feb 03
1
[LLVMdev] Issues with the llvm.stackrestore intrinsic - now LoopRotation handling of alloca
2012/2/3 Patrik Hägglund <patrik.h.hagglund at ericsson.com>: > Hi, > > I've tracked the first problem (mentioned in my previous email, quoted > below) down further, ending up in the handling of alloca in > LoopRotation.cpp (from trunk): > >      // If the instruction's operands are invariant and it doesn't read > or write >      // memory, then it is
2017 Feb 22
0
Crash in the latest release
I found this by accident yesterday. The program that crashes is the first two lines of the example from the help page for nlmer. That example hasn't changed in a long time, so I assumed that it is an R-devel issue. It could also be a long latent nlmer bug. The second run with valgrind is puzzling. Terry T. > library(lmer) > sessionInfo() R Under development (unstable)
2008 Apr 16
8
[Bug 15528] New: jpeg decoder allocation size overflows
http://bugs.freedesktop.org/show_bug.cgi?id=15528 Summary: jpeg decoder allocation size overflows Product: swfdec Version: git Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: library AssignedTo: swfdec at lists.freedesktop.org
2017 Feb 22
0
[Lme4-authors] Crash in the latest release
Thanks, posted to https://github.com/lme4/lme4/issues/412 for further discussion ... On Wed, Feb 22, 2017 at 10:03 AM, Therneau, Terry M., Ph.D. <therneau at mayo.edu> wrote: > I found this by accident yesterday. The program that crashes is the first > two lines of the example from the help page for nlmer. That example hasn't > changed in a long time, so I assumed that it is
2013 May 30
2
[LLVMdev] unexpectedly loop hanging
Hello Duncan, Thank you for your quick answer. I use the standard Makefile from a pass, that is calling Makefile.common. I saw only the make -d option, that "*print lots of debugging information*", as mentioned by LLVM. Using this, valgrind don't tell me extra info. It is a very good idea ti use -g, but where to insert? If I am trying to use clang++, I have to fix a lot of things.
2004 Sep 10
4
reading vorbis comments with FLAC++?
Hi me (2x - Haberman and Coalson), On Tue, Nov 11, 2003 at 03:51:42PM -0800, Josh Coalson wrote: > The C++ interface is a little simpler: [code follows] OK. Well, I found the C interface a little bit easier to understand, so I ended up using that instead of continuing to try to figure out the C++ interface. The one problem I have is that the values in block->data. vorbis_comment.comments
2019 Feb 27
2
Intermittent crashes with inset `[<-` command
Valgrind (without gctorture) reports memory misuse: % R --debugger=valgrind --debugger-args="--leak-check=full --num-callers=18" ... > x <- 1:200000 > y <- rep(letters[1:5], length(x) / 5L) > for (i in 1:1000) { + # x[y == 'a'] <- x[y == 'b'] + x <- `[<-`(x, y == 'a', x[y == 'b']) + cat(i, '') + } 1 2 3 4 5 6 7 8 9 10