similar to: Conditional jump or move depends on uninitialised value

Displaying 20 results from an estimated 100 matches similar to: "Conditional jump or move depends on uninitialised value"

2018 Aug 15
1
error while compiling dovecot
hello my server is centos 6 64 bit while installing dovecot i get this error Failed to run: ./test-compression what could be the reason. could someone guide me please Version dovecot-ce-2.3.0-1 0 / 7 tests failed ==21130== Conditional jump or move depends on uninitialised value(s) ==21130== at 0x349B00ACB2: ??? (in /usr/lib64/liblzma.so.0.0.0) ==21130== by 0x349B00AEA9: ??? (in
2005 Jun 15
6
Compressed maildir
Greetings, I noticed a while back someone posted a patch/plugin that allowed Dovecot to use compressed mbox files. I'm now wondering how far that would put us from having compressed maildir? I have a server with more CPU than disk space, and while I can buy more HDD space, my backup solution doesn't make that practical. It seems to me that when looking for a message file, if it
2009 Dec 08
3
Developer Documentation
Hi Everyone.... I Try to make a modification in dovecot Maildir system.... I want to include lines from another file into every email when the user request to read this email. Is Like put some extras itens email. I try to find how to do this but what i understand is, every email is read "on the fly", but i dont find exactly where... i didnt find some "read" to do this. Some
2006 Aug 18
1
uninitialised constant?
Hi. I''m having problems with a class constant I''ve defined as follows: class Customer < ActiveRecord::Base has_many :orders TITLES = [''Mr'', ''Ms'', ''Miss'', ''Mrs''] end Whenever I try and access this constant using Customer::TITLES, I get an unitialized constant Customer::TITLES error. Is my syntax
2013 Sep 01
0
[PATCH] drm/nv50: Fix backlight not working when PWM_DIV is uninitialised
Known issues before merge: - Currently requires acpi_backlight=vendor kernel param - 0x5e always valid? Signed-off-by: Roy Spliet <r.spliet at student.tudelft.nl> Tested-by: Rick Hendricksen --- drivers/gpu/drm/nouveau/nouveau_backlight.c | 20 +++++++++++++++++--- drivers/gpu/drm/nouveau/nouveau_display.c | 4 ++++ drivers/gpu/drm/nouveau/nouveau_display.h | 7 +++++++ 3 files
2006 Nov 30
0
[LLVMdev] Conditional jump or move depends on uninitialised value
llvm-gcc is producing segmentation fault when running with -emit-llvm. Running cc1 in valgind produces the warning: ==12768== at 0x8D042C: llvm::llvm_ostream& llvm::llvm_ostream::operator<< <llvm::Module>(llvm::Module const&) (Streams.h:41) ==12768== by 0x8D0464: llvm::PrintModulePass::runOnModule(llvm::Module&) (PrintModulePass.h:41) ==12768== by 0xED6EB9:
2015 Nov 19
2
[Bug 2500] New: ConnectionAttempts=0 causes ssh to output uninitialised data on stdout
https://bugzilla.mindrot.org/show_bug.cgi?id=2500 Bug ID: 2500 Summary: ConnectionAttempts=0 causes ssh to output uninitialised data on stdout Product: Portable OpenSSH Version: 7.1p1 Hardware: amd64 OS: Linux Status: NEW Severity: normal Priority: P5 Component: ssh
2020 Aug 07
0
[PATCH] vdpa/mlx5: Fix uninitialised variable in core/mr.c
On 2020/8/7 ??2:56, Alex Dewar wrote: > If the kernel is unable to allocate memory for the variable dmr then > err will be returned without being set. Set err to -ENOMEM in this > case. > > Fixes: 94abbccdf291 ("vdpa/mlx5: Add shared memory registration code") > Addresses-Coverity: ("Uninitialized variables") > Signed-off-by: Alex Dewar <alex.dewar at
2014 Dec 01
0
v2.2.15 - make check - Conditional jump or move depends on uninitialised value
On 11/30/2014 05:53 AM, AMM wrote: > __strspn_sse42 (in /lib64/libc-2.14.90.so) Is it possible that you are encountering this issue? https://bugs.kde.org/show_bug.cgi?id=270925 Either way, the error seems to stem from your libc implementation (if it is not the valgrind bug). If possible, upgrade your valgrind, libc etc. br, Teemu Huovila
2014 Dec 01
2
v2.2.15 - make check - Conditional jump or move depends on uninitialised value
On Monday 01 December 2014 03:41 PM, Teemu Huovila wrote: > On 11/30/2014 05:53 AM, AMM wrote: >> __strspn_sse42 (in /lib64/libc-2.14.90.so) > Is it possible that you are encountering this issue? https://bugs.kde.org/show_bug.cgi?id=270925 > Either way, the error seems to stem from your libc implementation (if it is not the valgrind bug). > > If possible, upgrade your
2014 Dec 01
0
v2.2.15 - make check - Conditional jump or move depends on uninitialised value
On 12/01/2014 12:41 PM, AMM wrote: > > On Monday 01 December 2014 03:41 PM, Teemu Huovila wrote: > But Dovecot 2.2.10 (and earlier versions) were not throwing this error. This test was added in Dovecot version 2.2.14. It is also the only reference to strspn() in the whole project. > Can I can ignore it by NOT doing "make check"? I would say you can safely ignore it, but I
2008 Jan 07
0
uninitialised theora_info values
Hi, Ralph recently checked in a version of theora/tests/noop.c that uses the new API. Part of the reason for this test is to check for memory leaks in the library's constructors and destructors. You can run the test suite under valgrind by configuring with --enable-valgrind-testing. The test passes, but gives output like: make[1]: Entering directory
2014 Nov 30
2
v2.2.15 - make check - Conditional jump or move depends on uninitialised value
Hello, I am currently using Dovecot 2.2.10 on Fedora 16 - 64 bit system I had made v2.2.10 Fedora 16 rpm file using spec file from ATrpms. http://dl.atrpms.net/all/dovecot.spec It has been working well from 6 months or so. Today I tried to make v2.2.15 rpm using same spec file. But "make check" is giving following error: fatal_printf_format_fix
2014 Mar 14
1
Conditional jump or move depends on uninitialised value(s)
Hi, I'm using valgrind to check over some C/C++ code for an R library. I'm getting the report (see below), but can't track down the uninitialised value(s). I tried using --track-origins=yes in valgrind which gives: ==28258== Uninitialised value was created by a stack allocation ==28258== at 0xEE33D98: ??? (in /usr/lib64/R/lib/libRlapack.so) I presume the problem is an
2009 Jan 27
1
uninitialised value in R (PR#13476)
Hi, I get an "Conditional jump or move depends on uninitialised value(s)" from valgrind when using 'solve' in combination with some simple C-code. (I did not use other functions of R besides 'solve'.) In detail: running R --vanilla -d "valgrind --tool=memcheck --memcheck:leak-check=yes --num-callers=20 " and calling .Call("XXX") nd <- 3
2013 Sep 26
1
Conditional jump or move depends on uninitialised value(s)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Timo, Dovecot 2.2.6 compiled on Ubuntu 10.04 fails on "make check" with the following errors. "make install" is finishing just fine and Dovecot itself works flawlessly so far. - ----- 8< ----- http header invalid [0]: parse failure ............................... : ok: Expected ':' after header field name
2006 Aug 25
3
uninitialised constant LoginEngine
In my worker class, when i try to start the worker thread, it throws the error: uninitialized constant LoginEngine - (NameError) /usr/lib/ruby/gems/1.8/gems/activesupport-1.3.1/lib/active_support/dependencies.rb:123:in `const_missing'' /usr/lib/ruby/gems/1.8/gems/activesupport-1.3.1/lib/active_support/dependencies.rb:131:in `const_missing''
2019 Nov 03
4
[Bug 112201] New: Syscall param ioctl(generic) points to uninitialised byte(s)
https://bugs.freedesktop.org/show_bug.cgi?id=112201 Bug ID: 112201 Summary: Syscall param ioctl(generic) points to uninitialised byte(s) Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: not set Priority: not set
2016 Nov 21
2
Conditional jump or move depends on uninitialised value(s)
I spent some time digging into a Valgrind report of uninitialized values in LLVM r287520 built using itself. (One of quite a few such reports that comes up during a "make check".) I could use another set of eyes on the issue if someone has time. This command gives me an error: valgrind -q ./bin/llc < /home/regehr/llvm/test/CodeGen/Hexagon/hwloop-dbg.ll -march=hexagon
2013 Jun 25
4
Syslinux 6.00 released
On Tue, 25 Jun, at 01:52:00PM, Helmut Hullen wrote: > Thanks - now it crashes later ... What crash are you seeing? > I don't have the ia64 files which are needed for a complete binary. But > maybe that's only my special problem. You shouldn't need ia64 files to build ia32 and x86-64 versions of gnu-efi or Syslinux. -- Matt Fleming, Intel Open Source Technology Center