1. Forum
  2. Usenet
  3. COMP.LANG.C

  • Re: A glimpse of sanity

    From Stefan Ram@21:1/5 to Stefan Ram on Tue May 28 14:55:40 2024
    ram@zedat.fu-berlin.de (Stefan Ram) wrote or quoted:
    Whenever I add "-fsanitize=address" or "-fsanitize=undefined"
    on Windows, the executables will run, but not do anything,

    I mean the executables created, i.e, "a.out".

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From bart@21:1/5 to Stefan Ram on Tue May 28 16:14:31 2024
    On 28/05/2024 15:55, Stefan Ram wrote:
    ram@zedat.fu-berlin.de (Stefan Ram) wrote or quoted:
    Whenever I add "-fsanitize=address" or "-fsanitize=undefined"
    on Windows, the executables will run, but not do anything,

    I mean the executables created, i.e, "a.out".

    That sounds fishy. Executables on Windows are usually called "a.exe", by
    gcc at least, unless they are named. (Only 'as' on Windows will create a default output called "a.out").

    What is the size of the executable produced, and is it as expected?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Stefan Ram@21:1/5 to All on Tue May 28 14:49:33 2024
    LLVM-MinGW is a toolchain built with Clang, LLD, libc++, targeting
    i686, x86_64, arm and aarch64 (ARM64) running on Windows.

    They say it supports Address Sanitizer und Undefined Behaviour
    Sanitizer.

    Whenever I add "-fsanitize=address" or "-fsanitize=undefined"
    on Windows, the executables will run, but not do anything,
    just return immediately. Neither is normal output printed nor
    are diagnostics when trying to trigger the sanitizers. Without
    those options, the programs will run fine.

    It tried adding "-lclang_rt.asan-x86_64", but then it complains
    about duplicate symbols, so I guess that this is not needed.

    I also made sure the directory containing
    "libclang_rt.asan_dynamic-x86_64.dll" is in the PATH.

    So, I can't get the sanitizers to work here! I'll just try
    downloading another version in a few months . . .

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Kaz Kylheku@21:1/5 to Stefan Ram on Tue May 28 16:30:55 2024
    On 2024-05-28, Stefan Ram <ram@zedat.fu-berlin.de> wrote:
    ram@zedat.fu-berlin.de (Stefan Ram) wrote or quoted:
    Whenever I add "-fsanitize=address" or "-fsanitize=undefined"
    on Windows, the executables will run, but not do anything,

    I mean the executables created, i.e, "a.out".

    Windows won't execute a .out file. Windows Explorer will, if you've
    associated the .out suffix with a program to handle it.

    --
    TXR Programming Language: http://nongnu.org/txr
    Cygnal: Cygwin Native Application Library: http://kylheku.com/cygnal
    Mastodon: @Kazinator@mstdn.ca

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Kenny McCormack@21:1/5 to 643-408-1753@kylheku.com on Tue May 28 18:03:14 2024
    In article <20240528092957.862@kylheku.com>,
    Kaz Kylheku <643-408-1753@kylheku.com> wrote:
    On 2024-05-28, Stefan Ram <ram@zedat.fu-berlin.de> wrote:
    ram@zedat.fu-berlin.de (Stefan Ram) wrote or quoted:
    Whenever I add "-fsanitize=address" or "-fsanitize=undefined"
    on Windows, the executables will run, but not do anything,

    I mean the executables created, i.e, "a.out".

    Windows can't directly execute a .out file. Windows Explorer will, if you've >associated the .out suffix with a program to handle it.

    As will CMD.EXE.

    Don't know about PowerShell.

    --
    I'm building a wall.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)