The 20 May 2024 build (13521) is out.

[killerbot]

We switched to gcc 14.1.0 (on 20 May 2024) --> download the new wx/mingw dll's see link below

Get the compiler we use here : https://github.com/brechtsanders/winlibs_mingw/releases/download/14.1.0posix-18.1.5-11.0.1-ucrt-r1/winlibs-x86_64-posix-seh-gcc-14.1.0-mingw-w64ucrt-11.0.1-r1.7z

Get quick announcements through the RSS feed http://www.codeblocks.org/nightly/CodeBlock_RSS.xml

Before you use a nightly make sure you understand how it works.

A link to the unicode windows wxWidget dll(s) for Code::Blocks : https://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/Prerequisites/wxmsw32u_gcc_cb_wx325_2D_gcc1410-mingw64.7z
A link to Mingw64 dll's needed by Code::Blocks : http://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/Prerequisites/Mingw64dlls14.1.0.7z


The 20 May 2024 build is out.
  - Windows :
   http://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/2024/CB_20240520_rev13521_win64.7z
  - Linux :
   none

The current SDK version is : 2.25.0

Resolved Fixed:

• build with wx 3.2.5 and gcc 14.1.0/color]

Regressions/Confirmed/Annoying/Common bugs:

[ollydbg]

Nice work! Killerbot.

[MehdiChinoune]

CodeBlocks was detected by "Windows Defender" as a virus.
(It could be a false positive)

[stahta01]

CodeBlocks was detected by "Windows Defender" as a virus.
(It could be a false positive)

Online or offline version?
Which of the 4 downloads?

Tim S.

[MehdiChinoune]

Online or offline version?

I don't understand, Are you talking about CodeBlocks or Windows defender. I only know that both have one version.

Which of the 4 downloads?

CB_20240520_rev13521_win64.7z

[nenin]

CodeBlocks was detected by "Windows Defender" as a virus.
(It could be a false positive)

Corporate ESET does not react.

[ThierryD]

Hi,

Me too, Bit Defender alert me about two "last" nigthly build. I must force "de"push in "quarantain" to restore file signaled by virus Gen:Variant.Barys.459296
With 9 may version, only C:\Codeblocks\Codeblocks.dll is affected.

But, with 19 may version, not only this file, but also C:\Codeblocks\Share\CodeBlocks\Plugins\Exporter.dll, C:\Codeblocks\Share\CodeBlocks\Plugins\NassiShneiderman.dll, C:\Codeblocks\Share\CodeBlocks\Plugins\wxSmithAui.dll, C:\Codeblocks\Share\CodeBlocks\Plugins\wxSmithContribItems.dll and C:\CodeBlocks\Share\CodeBlocks\codesnippets.dll are advertised with same "virus". GRRR!
Many files  ...  I'm not quiet ...

"False positive" or not ?

Thank's.

PS : My apologies about CB Team, if they are ...  "Waste of time", sure !!!

[killerbot]

I think false positives. Anyone with experience and knowledge what could trigger this, and how we can avoid this ?

[nina]

Hello,

I think false positives. Anyone with experience and knowledge what could trigger this, and how we can avoid this ?

I don't think so. The other Mingw-w64 distributions don't have these problems.
Did you read my previous message (May 09, 2024) ?

Hi,

First of all, thank you very much for your work.
I signed up just to let you know that some versions of Winlibs contain viruses, so you'll have to be very careful. Among other things, there is a potential risk of malicious code injection into CB.
Thank you again.

--- > https://github.com/brechtsanders/winlibs_mingw/issues/199
https://github.com/brechtsanders/winlibs_mingw/issues/201
https://www.virustotal.com/gui/file/16c15e587a488ca24b49f7b178028efa719aed3eb9db7ce79449fce097909cbd/relations
(Have a look at the bundled files: for example, nvptx-arch.exe (related to llvm but) has 15/72 detections, this contrasts sharply with the 2/35 of the package.)

[ChosenName]

Windows Defender flagged the "CB_20240520_rev13521_win64.7z" file as containing "Trojan:Script/Wacatac.B!ml" and blocked the download. I allowed the download and scanned the file - which reported no issues.

Uncompressed the 7z file to a fresh folder and scanned: no issues.

[stahta01]

Windows Defender flagged the "CB_20240520_rev13521_win64.7z" file as containing "Trojan:Script/Wacatac.B!ml" and blocked the download. I allowed the download and scanned the file - which reported no issues.

Uncompressed the 7z file to a fresh folder and scanned: no issues.

This leads me to think it might be MS FUD issue. https://en.wikipedia.org/wiki/Fear,_uncertainty,_and_doubt

Tim S.

[nenin]

I don't think so. The other Mingw-w64 distributions don't have these problems.

This is not correct. Some nixMan builds also face this problem.
https://github.com/niXman/mingw-builds-binaries/issues
Likely it is related to the "heuristic" detection, which was problematic ab initio.

[ThierryD]

Thank's for your comments and responses.

After search on Net about this "false or true" malware  "Gen:Variant.Barys.459296", I download MalwareBytes yesterday and run it (tempory test of tool).
Result : PUP detected on my two computers.
I decide to suppress all files detected with this tool. I rerun and no alert appear ... Good!

Today, I download (with Firefox) last nightly (20 may), and result is the same : download blocked another time with same alert.  It's annoying!
I conserve version 13518 (05 may) of CB to continue "my work" (current test : integrate last version of OneAPI Intel C/C++ compiler into IDE, it's work !).

Thank's.

Thierry D.

[Miguel Gimenez]

False positives are a plague, specially with libraries. If any malware uses a library, some AV vendors will flag all software using said library as a virus.

I use UPX for packing the executables in my company's web page: Recently they are being flagged as virus even if some of them have not changed in the last ten years. This is because some malware uses UPX, not because UPX itself is infected.

[nenin]

False positives are a plague, specially with libraries. If any malware uses a library, some AV vendors will flag all software using said library as a virus.

I use UPX for packing the executables in my company's web page: Recently they are being flagged as virus even if some of them have not changed in the last ten years. This is because some malware uses UPX, not because UPX itself is infected.

Week ago I built some lib with CMake. CMake compile some small codes to verify access to C functions like v*printf. So, one of these small exe (5 line of code) was catch by AV as the threat and exterminated.   :-X  However, CMake was happy and library was built finally. 10 year ago some most paranoid AV attacked gdb.  Now more or less normal AVs have problems with very plain code just because compiler differs from their expectations.