similar to: -Wmisleading-indentation violations

Hi, I'm currently trying to find and fix memory leaks (compiling with ``-fsanitize=address``) in the KLEE tool [1] an having found some leaks and I'm having trouble suppressing them. I'm trying to suppress them using the ``-fsanitize-blacklist=blacklist.txt`` option as documented at [2]. I'm using Clang 3.7 ( Arch Linux package 3.7.0-6). The sort of reported leaks I see are ```

Hi Kostya & Yury, Thanks for the advice. On 9 February 2016 at 22:48, Kostya Serebryany <kcc at google.com> wrote: > Hi Dan, > > On Tue, Feb 9, 2016 at 10:57 AM, Dan Liew <dan at su-root.co.uk> wrote: >> >> Hi, >> >> # TL;DR >> >> I've been building an application with and without the address >> sanitizer (with gcc 5.3 and

Hi, I've taken a look at the binary tarballs for clang+llvm-3.6.2-rc1-* that have been uploaded and observed the following: * All uploaded tarballs include the generated CMake files apart from ``clang+llvm-3.6.2-rc1-x86_64-linux-gnu-ubuntu-14.04.tar.xz``. These files (share/llvm/cmake/*.cmake) are missing in this tarball. * Inside the Ubuntu tarball the directory is not consistently named

Hi, # TL;DR I've been building an application with and without the address sanitizer (with gcc 5.3 and clang 3.7.1) and I've observed that the application's behaviour changes (assertion hit/ not hit). I'm wondering if this could be a bug in address sanitizer or if the application I'm running is just buggy (e.g. doing bad things like relying on memory layout, etc.). I'm

Hi, I'm having problems compiling llvm-gcc-4.2-2.9 (from [1]). I need to use this version because I am trying to use KLEE (see [3]) which needs these versions. I am compiling on Arch Linux using gcc (GCC) 4.7.0 20120505 (prerelease) the output of `gcc -v` can be found at http://pastebin.com/8j2m3wzD I have tried the following 1. Extracted llvm-2.9 (from [2]) 2. Applied a patch (adds

Debian bug 812166[0] reported this build failure due to Wmisleading-indentation with gcc-6: non-fatal.c: In function 'init_nonfatal_mce_checker': non-fatal.c:103:2: error: statement is indented as if it were guarded by... [-Werror=misleading-indentation] switch (c->x86_vendor) { ^~~~~~ non-fatal.c:97:5: note: ...this 'if' clause, but it is not if (

I did a RelWithDebInfo + asserts build of LLVM just now and, when running "make check" under Valgrind, am seeing a lot of uses of uninitialized memory like the one below. Anyone know offhand what's likely to be the root cause? Unfortunately a Debug build doesn't give these errors. Thanks, John FAIL: LLVM :: Analysis/BasicAA/pr18573.ll (2093 of 18733)

Hi, On Sun, Jan 17, 2016 at 1:04 PM, Dan Liew <dan at su-root.co.uk> wrote: > On 16 January 2016 at 20:21, Ismail Donmez <ismail at i10z.com> wrote: >> On Sat, Jan 16, 2016 at 9:33 PM, Dan Liew <dan at su-root.co.uk> wrote: >>>> I am trying to enable this on openSUSE but it seems to break >>>> standalone lldb (note that we don't ship static

Well, it looks like almost all of the problems go away when I build using trunk instead of 3.9. So, that was scary but I'm going to forget it ever happened. >8000 test cases failed under Valgrind!! John On 11/20/2016 03:03 AM, Sanjoy Das via llvm-dev wrote: > Hi John, > > This is probably somewhat of a stretch, but since the problem does not > happen with a Debug build,

On Sat, 4 May 2024, openssh at tr.id.au wrote: > Hey there, > > I often want different behavior in my ssh client depending on > whether I'm logging into an interactive session or running > a remote non-interactive command. We can see at, say, > https://unix.stackexchange.com/a/499562/305714 that this isn't a > unique wish, and existing solutions are kind of baroque.

Hey Damien, > Would something like this help? > > Match sessiontype shell > User foo > Match remotecommand "none" > User foo2 > Match sessiontype exec remotecommand "/rsync" > User bar > Match sessiontype subsystem remotecommand "sftp" > User baz > > > diff --git a/readconf.c b/readconf.c > <snip> Thanks for looking

Hi all- A few weeks ago I noticed that our "omit braces with single line blocks" rule wasn't written down! Additionally, as a group on IRC and in review, noticed that the enforcement of this rule has been extremely inconsistent. We made a first run at codifying our existing practice here: https://reviews.llvm.org/D80947, which was then committed after significant time on

https://bugzilla.mindrot.org/show_bug.cgi?id=3604 Bug ID: 3604 Summary: Building OpenSSH fails with zlib1.3 installed Product: Portable OpenSSH Version: 9.4p1 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 Component: Build system Assignee: unassigned-bugs at

On Thu, Sep 24, 2020 at 2:58 PM Ján Tomko <jtomko@redhat.com> wrote: > On a Thursday in 2020, Wei Wang wrote: > >Seems it didn't appear on the mailing list, resent it. > > > > Hi folks, > > > >I'm trying to build libvirt using meson with the latest upstream libvirt, > >but the compilation fails: > >(followed on

On 22/01/16 14:38, Ian Campbell wrote: > Debian bug 812166[0] reported this build failure due to > Wmisleading-indentation with gcc-6: > > non-fatal.c: In function 'init_nonfatal_mce_checker': > non-fatal.c:103:2: error: statement is indented as if it were guarded by... [-Werror=misleading-indentation] > switch (c->x86_vendor) { > ^~~~~~ > >

https://bugzilla.mindrot.org/show_bug.cgi?id=3689 Bug ID: 3689 Summary: Implicit function declarations: SHA256, SHA512 with -DWITH_XMSS Product: Portable OpenSSH Version: -current Hardware: Other OS: Linux Status: NEW Severity: minor Priority: P5 Component: sshd

https://bugzilla.mindrot.org/show_bug.cgi?id=3744 Bug ID: 3744 Summary: openssh-SNAP-20241015 sshd-auth.c:467:2: error: use of undeclared identifier 'saved_argc'; did you mean 'saved_argv'? Product: Portable OpenSSH Version: 9.9p1 Hardware: ARM64 OS: Mac OS X

On Wed, 2016-01-20 at 20:16 -0800, Martin Michlmayr wrote: > Package: xen > Version: 4.6.0-1 > Severity: important > User: debian-gcc at lists.debian.org > Usertags: ftbfs-gcc-6 gcc-6-misleading-indentation > > This package fails to build with GCC 6.??GCC 6 has not been released > yet, but it's expected that GCC 6 will become the default compiler for > stretch. >

Personally, I favor "always use braces" because it helps readability for me. The compiler may be good at flagging misleading indentation, but my visual processing system is terrible at it, especially since we use a measly two spaces for indentation. And we grant indentation exceptions for--among other things--case labels in switches. When some nested statements have braces and others

On Thu, Dec 15, 2016 at 4:22 PM, Zev Weiss <zev at bewilderbeest.net> wrote: [...] > I tested (or tried) git commit b737e4d7 on three systems, with somewhat > mixed results. Thanks for the comprehensive testing! > On Mac OSX (macOS?) 10.9, configure failed with: > > ... > checking OpenSSL header version... 1000208f (OpenSSL 1.0.2h 3 May 2016) > checking