May 2026 - Pharo-dev - lists.pharo.org

Re: "My First Pair Programming Session with Claude in Pharo" â New blog post on all: objects all: theTime

by steven.costiou＠kloum.io

Hi, it's really minor that AI can hallucinate, destroy your database, produce bad code and a whole new generation of unskilled sloppy coders, and among other things, make you dumb. Despite that AI can still do impressive things. But why would you use AI when you know its tremendous ecological (especially water consumption and heat production) and sociological cost? What about: stop paying for AI, stop funding AI, take back the money from OpenAI and all (they have too much) and let's correctly train powerful new programmers to become our cool future colleagues, all without giant data-centers that consume whole cities' resources? And I don't think that these questions cannot be answered in a productive way and unheated (ha ha) way. Steven. Le 2026-05-29 10:16, Danil Osipchuk a Ã©crit : > Koen, greetings > > Thank you for your consistent effort with your blog, it is a pleasure > to read. > > With AI there are many facets, some of which are more controversial > than others, this list seems to politely stay silent to avoid heated > unproductive discussions. > However, I can't help not to suggest the story here > https://www.theguardian.com/technology/2026/apr/29/claude-ai-deletes-firm-d… > and the observation that the agent's explanation why it did delete the > database sounds like a bold metaphysical statement. > > Fun times. > > regards, > Danil > > ÑÑ, 28 Ð¼Ð°Ñ 2026â¯Ð³. Ð² 00:13, Koen De Hondt > <koen(a)all-objects-all-the-time.st>: > >> Dear Pharo users and developers, >> >> I posted the third article in a series about using AI in Pharo >> development. After building the MCP server together, it was time to >> pair program with Claude to write some code in a Pharo image. In the >> new post, I share my experience of working with Claude and how it has >> impacted my development process. >> >> https://all-objects-all-the-time.st/#/blog/posts/26 >> >> As always, all feedback is welcome. >> >> Happy reading! >> >> Ciao, >> Koen

May 29, 2026

Re: "My First Pair Programming Session with Claude in Pharo" â New blog post on all: objects all: theTime

by Danil Osipchuk

Koen, greetings Thank you for your consistent effort with your blog, it is a pleasure to read. With AI there are many facets, some of which are more controversial than others, this list seems to politely stay silent to avoid heated unproductive discussions. However, I can't help not to suggest the story here https://www.theguardian.com/technology/2026/apr/29/claude-ai-deletes-firm-d… and the observation that the agent's explanation why it did delete the database sounds like a bold metaphysical statement. Fun times. regards, Danil ÑÑ, 28 Ð¼Ð°Ñ 2026â¯Ð³. Ð² 00:13, Koen De Hondt <koen(a)all-objects-all-the-time.st >: > Dear Pharo users and developers, > > I posted the third article in a series about using AI in Pharo > development. After building the MCP server together, it was time to pair > program with Claude to write some code in a Pharo image. In the new post, I > share my experience of working with Claude and how it has impacted my > development process. > > https://all-objects-all-the-time.st/#/blog/posts/26 > > As always, all feedback is welcome. > > Happy reading! > > Ciao, > Koen >

May 29, 2026

Pharo-LLM in Pharo-Launcher

by omar abedelkader

Hello everyone, You can now officially download the development version of Pharo-LLM, which currently includes ChatPharo, directly from Pharo Launcher. In the future, Pharo-LLM will also include additional tools that you will be able to use within an already built-in Pharo image. ï¿¼ Enjoy :) â Omar AbedelKader https://github.com/pharo-llm

May 28, 2026

"My First Pair Programming Session with Claude in Pharo" â New blog post on all: objects all: theTime

by Koen De Hondt

Dear Pharo users and developers, I posted the third article in a series about using AI in Pharo development. After building the MCP server together, it was time to pair program with Claude to write some code in a Pharo image. In the new post, I share my experience of working with Claude and how it has impacted my development process. https://all-objects-all-the-time.st/#/blog/posts/26 As always, all feedback is welcome. Happy reading! Ciao, Koen

May 27, 2026

"Building an MCP Server with Claude" â New blog post on all: objects all: theTime

by Koen De Hondt

Dear Pharo users and developers, I posted the second article in a series about using AI in Pharo development. This article is a transcript of a large part of a pair programming session with Claude to build an MCP server for Pharo, called Iris. The transcript is very long. If it is too long, jump to the end of the article to read lessons learned and find links to the Iris project page and the code. https://all-objects-all-the-time.st/#/blog/posts/25 As always, all feedback is welcome. Happy reading! Ciao, Koen

May 20, 2026

need early testers for micro python 3 for freed

by Aaron Wohl

I (pronounced claude.ai) have been working on a port of the current micropython to FreeDOS. It is fairly complete but untested by users. Manuals: https://avwohl.github.io/freedos_micro_python/ Sources: https://github.com/avwohl/freedos_micro_python To extend the tests, I implemented wget, scp, and sftp, which are working. It is supposed to work with mTCP and any NIC, but I have only tested NE2000 There was some recent talk about a good language for FreeDOS. This doesn't have an IDE. But it does have a modern higher network stack (SSH, SSL, HTTPS).

May 19, 2026

Re: claude.ai code review of pharo-v

by Nicolas Anquetil

Coincidentally, this is discussed in a paper that will appear next week on arXiv: (and here for the impatients https://www.dropbox.com/scl/fi/2tjmdemfk4mfy7fxpm3vq/AIPolicy.pdf?rlkey=fx0… <https://www.dropbox.com/scl/fi/2tjmdemfk4mfy7fxpm3vq/AIPolicy.pdf?rlkey=fx0…>) AI Policy, Disclosure, and Human in the Loop: How Are Contribution Guidelines Adapting to GenAI? * Andre Hora * Romain Robbes /[...] This paper provides an initial empirical study to explore how open source projects are adapting to GenAI contributions. We analyzed 1,000 popular GitHub repositories and identified 118 AI policies for contributors. Our results show that (1) 78% of the AI policies allow contributions generated with GenAI, while 22% explicitly discourage their use; (2) 51% of the AI policies require the disclosure of AI-generated contributions; and (3) 74% of the AI policies require a human in the loop during contribution. [...]/ nicolas On 2026-05-14 09:38, Aaron Wohl via Pharo-dev wrote: > Human sign-off would be a great system.Â Unfortunately, the current > setup requires humans to generate fixes for Pharo.Â Â The discussion is > to allow AI-generated proposed fixes.Â I don't understand the > copyright issue, so I will let someone who does explain why AI fixes > are a copyright problem. > > The usual anti-AI copyright issues are 1) you can't copyright the work > of an AI and 2) AIs will always steal other peoples work and lie about > where it came from. > > ----- Original message ----- > From: Sven Van Caekenberghe <sven(a)stfx.eu> > To: Pharo Development List <pharo-dev(a)lists.pharo.org> > Cc: stephane ducasse <stephane.ducasse(a)inria.fr>, > guillermo.polito(a)inria.fr, Aaron Wohl <xphu(a)awohl.com> > Subject: Re: [Pharo-dev] claude.ai <http://claude.ai> code review of > pharo-v > Date: Thursday, May 14, 2026 2:52 AM > > AI Coding Assistants â The Linux Kernel documentation > <https://docs.kernel.org/process/coding-assistants.html> > docs.kernel.org <https://docs.kernel.org/process/coding-assistants.html> > <https://docs.kernel.org/process/coding-assistants.html> > > > It is great that you did this and important. But each change has to be > validated by a capable VM developer, who takes responsibility. > >> On 14 May 2026, at 04:42, Aaron Wohl via Pharo-dev >> <pharo-dev(a)lists.pharo.org> wrote: >> >> It has been in the news that Anthropic delayed the release of Mythos >> to invite groups to fix the AI's bugs. Â The news reports suggest that >> the big open-source projects are accepting AI bug fixes (not just bug >> reports). Â If the linux kernal and chrome are accepting AI code how >> can they do it and pharo can not? >> https://www.linuxfoundation.org/blog/project-glasswing-gives-maintainers-ad… >> I am not suggesting that AI code should be blindly accepted, some of >> AI bugs and fixes are fine. Â It is faster to have a human review than >> to generate fixes. >> >> ----- Original message ----- >> From: stephane ducasse <stephane.ducasse(a)inria.fr> >> To: Aaron Wohl <xphu(a)awohl.com> >> Cc: guillermo.polito(a)inria.fr, Pharo-dev <pharo-dev(a)lists.pharo.org> >> Subject: Re: [Pharo-dev] claude.ai code review of pharo-v >> Date: Wednesday, May 13, 2026 3:26 PM >> >> thanks we will check this. >> >> >>> On 13 May 2026, at 19:24, Aaron Wohl <xphu(a)awohl.com> wrote: >>> >>> I had Claude create PRs for the current git main and for the version >>> 12 you asked for. >>> I didn't submit them because they are AI-generated. Â I have no >>> interest in doing manual work that an AI can do. Â On copyright: if >>> not being able to copyright AI work is the issue, perhaps you could >>> copyright the collection (of source lines)? >>> >>> For pharo-12 there are 93 bug fixes posted here. >>> https://www.awohl.com/pharo-bugs-2026-05-13/ >>> >>> ----- Original message ----- >>> From: stephane ducasse <stephane.ducasse(a)inria.fr> >>> To: Aaron Wohl <xphu(a)awohl.com> >>> Cc: guillermo.polito(a)inria.fr, Pharo Development List >>> <pharo-dev(a)lists.pharo.org> >>> Subject: Re: [Pharo-dev] claude.ai code review of pharo-v >>> Date: Wednesday, May 13, 2026 8:14 AM >>> >>> Hi aaron >>> >>> Today I discussed with Guille (who was and still a bit sick and >>> under recovery) and did not have the opportunity to discuss with >>> Pablo (who is on vacation) >>> >>> We are interested in pullrequests that improve the security and code >>> of the VM and pluggins. >>> So your analyses are definitively worth. >>> >>> We would love to have PRs and for us this is great if you do them >>> and not an IA so that we can control the copyright concerns. >>> >>> So thank you for your time and idea. >>> Guille may contact you directly. >>> >>> S (this week we have 3 working days) and next week we have also some >>> non-working days. >>> The month of may is a gruyere. >>> >>> >>>> On 12 May 2026, at 09:10, Aaron Wohl via Pharo-dev >>>> <pharo-dev(a)lists.pharo.org> wrote: >>>> >>>> I regularly have Claude.AI review my code https://awohl.com, I >>>> pointed Claude at the Pharo-VM to see what it could see. Â A lot of >>>> the issues it found are things like strcpy without bounds checks >>>> with strings no one would ever make that big. However, it found >>>> some issues that are always triggered. >>>> >>>> Full list of issues >>>> https://github.com/avwohl/iospharo/blob/main/docs/pharo-vm-code-reivew-2026… >>>> >>>> I did not make an AI-generated patch list. stephane.ducasse(a)free.fr >>>> mentioned copyright concerns by guillermo.polito(a)inria.fr of >>>> accepting AI code. Â I assume this is due to the inability to >>>> copyright AI-generated work and to AI's tendency to steal others' >>>> work and lie about its origins. Â Â However, a lot of the fixes are >>>> so trivial, like off-by-one errors, that I don't know how much of >>>> an issue it is. If you want me to PR fixes and or tests that >>>> trigger for the full list, or always list, let me know. >>>> >>>> Many of the issues would only happen if someone were trying to >>>> break things (MAXLEN symlinks, damaged image files). If one were a >>>> mindset, it could be called AI slop. Â However, here is a short list >>>> of things that always cause issues in everyday operation: for >>>> example, every plugin loaded damages heap memory, or the nightly >>>> build of signed code disables SSL checks, so a simple DNS hack >>>> could get malicious code signed. >>>> >>>> Source: ~/pharo.md (review of /Users/wohl/esrc/pharo-vm @ pharo-10, >>>> 2026-05-11) >>>> Filter: only items that fire in normal benign operation, not edge cases >>>> requiring huge/crafted strings or attacker-chosen sizes. >>>> >>>> ================================================================ >>>> A. ALWAYS â MEMORY DAMAGE / UNDEFINED BEHAVIOR >>>> ================================================================ >>>> >>>> 1. sqNamedPrims.c:56-57 â calloc(sizeof(ModuleEntry)+strlen(name)) >>>> then strcpy writes strlen+1; 1-byte heap overflow on every plugin >>>> load. [#3.26] >>>> 2. ffi/callbacks/callbacks.c:14-32 â stack-allocated >>>> CallbackInvocation registered in runner->callbackStack/global >>>> queue; sig_longjmp exit leaves dangling stack pointer after every >>>> same-thread callback. [#2.8] >>>> 3. ffi/typesPrimitives.c:174-188 â setHandler(receiver, structType) >>>> stores pointer before failed()/ffi_get_struct_offsets checks; any >>>> error path frees memory while receiver still holds the dangling >>>> handle. [#2.6] >>>> 4. threadSafeQueue.c:113-137 â queue->first and node->element read >>>> outside the mutex; lock-holder's free(node) leaves the other >>>> consumer walking freed memory on every concurrent dequeue (hit by >>>> every FFI workload). [#3.21] >>>> 5. SocketPluginImpl.c:1109-1123 â sqSocketDestroy frees PSP(s) >>>> after sqSocketAbortConnection queues a closeHandler against pss; >>>> AIO dispatch fires on freed memory. [#3.22] >>>> 6. ffi/utils.c:43-50 â readString returns an un-pinned image-memory >>>> pointer; GC between strlen() and the caller's strcpy invalidates >>>> the length and the address. [#5.27] >>>> 7. ffi/callbacks/callbacks.c:24-29 â runner->callbackStack chain >>>> updated without any lock; reentrant callbacks from multiple threads >>>> on the same Runner corrupt the linked list. [#5.4] >>>> 8. pathUtilities.c:233-237 â strrchr(name,'.') result stored in >>>> fileExtension, but the NULL guard tests the unrelated `extension` >>>> variable; strcmp(NULL,...) crashes on any directory entry without a >>>> dot (e.g. "Makefile"). Â [#4.2] >>>> 9. pathUtilities.c:163 â first[strlen(first)-1] reads first[-1] >>>> (one byte before the buffer) whenever first is "", reachable from >>>> parameters.c:210-212 fallback. [#4.3] >>>> 10. externalPrimitives.c:57,66 â module path assembled in a >>>> file-static moduleNameBuffer with no lock; concurrent loads >>>> scribble each other's path and dlopen/LoadLibrary sees a torn >>>> string. [#5.3] >>>> 11. debugUnix.c:88-95,122-162 â SIGSEGV/SIGBUS/SIGFPE handler calls >>>> fopen/vfprintf/backtrace_symbols_fd/ctime_r/semaphore_wait (none >>>> async-signal-safe) and uses SA_NODEFER so the handler can re-enter >>>> itself on every crash. [#5.1] >>>> 12. debugUnix.c:123,144,154 â sigaction.sa_mask never initialized >>>> via sigemptyset for term_handler_action and sigpipe_handler_action; >>>> kernel reads uninitialized stack to decide what to mask on every >>>> install. [#5.2] >>>> 13. debug.c:57-66 â glibc strerror_r returns a pointer that may not >>>> write to the supplied buffer; caller prints the buffer >>>> unconditionally, leaking uninitialized stack bytes on every error >>>> path. [#5.7] >>>> 14. SocketPluginImpl.c:2494-2496 â sqSocket lastError stored in a >>>> file-static, clobbered across sockets; every concurrent socket >>>> failure overwrites another socket's error state. [#5.17] >>>> 15. aioWin.c:457/465 â heap-interior alias into allHandles >>>> transiently equals a freshly malloc'd region; any early return >>>> between the two assignments leaves a free-of-interior or double-use >>>> hazard. [#1/Â§9 PARTIAL] >>>> >>>> >>>> ================================================================ >>>> B. ALWAYS â SECURITY / CORRECTNESS (NOT MEMORY DAMAGE) >>>> ================================================================ >>>> >>>> TLS / SqueakSSL >>>> --------------- >>>> 1. sqUnixSSL.c:89-143 â SSL_CTX_set_verify never called; >>>> SSL_get_verify_result returns X509_V_OK by default â no certificate >>>> validation on any TLS connection. [#2.9] >>>> 2. sqUnixSSL.c:102-107 â SSLv23_method with only SSLv2/v3 disabled; >>>> TLS 1.0 and 1.1 still accepted on every handshake. [#2.9 / #6.3] >>>> 3. sqUnixSSL.c:115 â cipher list "!ADH:HIGH:MEDIUM:@STRENGTH" >>>> permits MEDIUM ciphers. [#2.9] >>>> 4. sqUnixSSL.c:107 â no SSL_OP_NO_COMPRESSION (CRIME), no >>>> SSL_OP_NO_RENEGOTIATION, no SSL_OP_CIPHER_SERVER_PREFERENCE. [#6.3] >>>> 5. sqWin32SSL.c:269-275,215,349-353 â sqExtractPeerName copies >>>> serverName verbatim into peerName instead of extracting the cert >>>> subject; epp.pwszServerName=NULL disables SChannel's hostname >>>> check, so image-side peerName==serverName is meaningless on every >>>> connection. [#3.19] >>>> 6. sqMacSSL.c:154-201,262-272,363-383 â >>>> kSSLSessionOptionBreakOnServerAuth disables auto verification; >>>> manual SecTrustEvaluate runs with no SSL policy carrying the >>>> hostname, so hostname is never checked. [#3.20] >>>> 7. sqWin32SSL.c:216-218 â SP_PROT_TLS1_0/1_1/1_2 enabled for both >>>> client and server roles. [#6.1] >>>> 8. sqMacSSL.c:154-164 â SSLSetProtocolVersionMin(ctx, >>>> kTLSProtocol1) sets minimum to TLS 1.0. [#6.2] >>>> >>>> VM internals >>>> ------------ >>>> 9. memoryUnix.c:66-89,109-111 â JIT pages mmap'd >>>> PROT_READ|PROT_WRITE|PROT_EXEC permanently; >>>> sqMakeMemoryExecutableFromTo / NotExecutable hooks are commented >>>> out, so W^X is defeated on Linux/FreeBSD. [#5.24] >>>> 10. debug.c:45 â error(char*) forwards the argument as the format >>>> string into the vfprintf-style logger; exported API contract leaks >>>> a %n/%s primitive to any future caller-controlled string. [#4.10] >>>> 11. ffi/typesPrimitives.c:170-172 â getHandler() returns the first >>>> slot of any oop with no class tag check; libffi consumes >>>> attacker-shaped ffi_type fields on every struct cif build, giving a >>>> controlled-dispatch primitive to anyone who can register an FFI >>>> struct. [#2.5] >>>> >>>> Build / supply chain (every build / every CI run) >>>> ------------------------------------------------- >>>> 12. Jenkinsfile:84,249 â fetch-and-execute installer via `wget â¦ | >>>> bash` over plain HTTP. [#7] >>>> 13. scripts/runTests.sh:31 â `wget -O - https://get.pharo.org/64/80 >>>> | bash`, executed from PR workflows. [#7] >>>> 14. scripts/installCygwin.ps1:7-9 â Cygwin installer + mirror >>>> retrieved over plain HTTP. [#7] >>>> 15. cmake/importLibFFI.cmake / importLibGit2.cmake / >>>> importSDL2.cmake â dependencies pinned to mutable git tags, no >>>> commit-SHA. [#7] >>>> 16. macros.cmake:69-103 + every cmake/import*.cmake using >>>> files.pharo.org â DownloadProject calls omit URL_HASH for libgit2, >>>> libssh2, openssl, zlib, SDL2, cairo, pixman, libpng, freetype, >>>> fontconfig, harfbuzz, gcc-runtime. [#7] >>>> 17. cmake/importFreetype2.cmake:47-49 â direct savannah.gnu.org >>>> download with no URL_HASH. [#7] >>>> 18. docker/ubuntu-arm64/Dockerfile, >>>> docker/debian10-armv7/Dockerfile â base images unpinned (no @sha256 >>>> digest). [#7] >>>> 19. Jenkinsfile:97-403 â every upload uses `scp -o >>>> StrictHostKeyChecking=no` against files.pharo.org. [#7] >>>> 20. Jenkinsfile:138 + cmake/sign.cmake:8-11 â SIGN_CERT_PASSWORD >>>> passed through environment under a broad withCredentials() block. [#7] >>>> 21. .github/workflows/continuous-integration-workflow.yaml:2 â `on: >>>> [push, pull_request]` with no `permissions:` block; fork PRs can >>>> edit runTests.sh and execute with the workflow GITHUB_TOKEN scope. [#7] >>>> 22. .github/workflows/...:11,14,68 â EOL runners (ubuntu-18.04, >>>> windows-2016) and EOL actions (checkout@v1, upload-artifact@v1). [#7] >>>> 23. cmake/packaging.cmake:92 â CPACK_PACKAGE_CHECKSUM "SHA1". [#7] >>>> 24. scripts/installCygwin.ps1:35-48 â `cygwin -q` suppresses >>>> signature warnings during install. [#7] >>>> 25. CMakeLists.txt:206,266-296 + cmake/Linux.cmake:1 â no >>>> -D_FORTIFY_SOURCE=2, no -fstack-protector-strong, no -fPIE/-pie, no >>>> -Wformat-security, no -Wl,-z,relro / -z,now / -z,noexecstack on >>>> Linux release builds. [#7] >>>> 26. CMakeLists.txt:206,266-296 â -Wno-int-conversion and >>>> -Wno-pointer-sign actively silenced; both classes of warning catch >>>> real bugs. [#7] >>>> 27. cmake/Linux.cmake:1 â Linux rpath set to "." (relative to CWD) >>>> instead of "$ORIGIN". [#7] >>>> 28. CMakeLists.txt:206 â Windows/Cygwin builds lack /GS, /guard:cf, >>>> /DYNAMICBASE, /NXCOMPAT. [#7] > -- Nicolas Anquetil Evref team -- Inria Lille

May 16, 2026

Re: claude.ai code review of pharo-v

by Norbert Hartl

Hi, > Am 14.05.2026 um 04:43 schrieb Aaron Wohl via Pharo-dev <pharo-dev(a)lists.pharo.org>: > > It is faster to have a human review than to generate fixes. And this contradicts somehow how open source works well. It sounds strange at first but if you maintained ever an open source project you know that reviewing stuff other people provide is a lot of effort. And probably nothing you want to focus on at that moment. The natural barrier is that people need to get into it and understand before making a PR. This avoids PRs that were done without working on it enough. And that eases the job of the maintainer a lot because background noise is better controlled. So what you say might sound good but it rather leads to the tension that people do not care a lot because AI was creating it for them in a few minutes and then you put all the burden of reviewing on the maintainer. And that is a thing that makes being an open sourcr maintainer miserable. So in new times there need to be new rules to be able to benefit from the new possibilities without destroying a lot. Norbert

May 14, 2026

Re: claude.ai code review of pharo-v

by Aaron Wohl

Human sign-off would be a great system. Unfortunately, the current setup requires humans to generate fixes for Pharo. The discussion is to allow AI-generated proposed fixes. I don't understand the copyright issue, so I will let someone who does explain why AI fixes are a copyright problem. The usual anti-AI copyright issues are 1) you can't copyright the work of an AI and 2) AIs will always steal other peoples work and lie about where it came from. ----- Original message ----- From: Sven Van Caekenberghe <sven(a)stfx.eu> To: Pharo Development List <pharo-dev(a)lists.pharo.org> Cc: stephane ducasse <stephane.ducasse(a)inria.fr>, guillermo.polito(a)inria.fr, Aaron Wohl <xphu(a)awohl.com> Subject: Re: [Pharo-dev] claude.ai code review of pharo-v Date: Thursday, May 14, 2026 2:52 AM AI Coding Assistants â The Linux Kernel documentation <https://docs.kernel.org/process/coding-assistants.html> docs.kernel.org <https://docs.kernel.org/process/coding-assistants.html> <https://docs.kernel.org/process/coding-assistants.html> It is great that you did this and important. But each change has to be validated by a capable VM developer, who takes responsibility. > On 14 May 2026, at 04:42, Aaron Wohl via Pharo-dev <pharo-dev(a)lists.pharo.org> wrote: > > It has been in the news that Anthropic delayed the release of Mythos to invite groups to fix the AI's bugs. The news reports suggest that the big open-source projects are accepting AI bug fixes (not just bug reports). If the linux kernal and chrome are accepting AI code how can they do it and pharo can not? > https://www.linuxfoundation.org/blog/project-glasswing-gives-maintainers-ad… > I am not suggesting that AI code should be blindly accepted, some of AI bugs and fixes are fine. It is faster to have a human review than to generate fixes. > > ----- Original message ----- > From: stephane ducasse <stephane.ducasse(a)inria.fr> > To: Aaron Wohl <xphu(a)awohl.com> > Cc: guillermo.polito(a)inria.fr, Pharo-dev <pharo-dev(a)lists.pharo.org> > Subject: Re: [Pharo-dev] claude.ai code review of pharo-v > Date: Wednesday, May 13, 2026 3:26 PM > > thanks we will check this. > > >> On 13 May 2026, at 19:24, Aaron Wohl <xphu(a)awohl.com> wrote: >> >> I had Claude create PRs for the current git main and for the version 12 you asked for. >> I didn't submit them because they are AI-generated. I have no interest in doing manual work that an AI can do. On copyright: if not being able to copyright AI work is the issue, perhaps you could copyright the collection (of source lines)? >> >> For pharo-12 there are 93 bug fixes posted here. >> https://www.awohl.com/pharo-bugs-2026-05-13/ >> >> ----- Original message ----- >> From: stephane ducasse <stephane.ducasse(a)inria.fr> >> To: Aaron Wohl <xphu(a)awohl.com> >> Cc: guillermo.polito(a)inria.fr, Pharo Development List <pharo-dev(a)lists.pharo.org> >> Subject: Re: [Pharo-dev] claude.ai code review of pharo-v >> Date: Wednesday, May 13, 2026 8:14 AM >> >> Hi aaron >> >> Today I discussed with Guille (who was and still a bit sick and under recovery) and did not have the opportunity to discuss with Pablo (who is on vacation) >> >> We are interested in pullrequests that improve the security and code of the VM and pluggins. >> So your analyses are definitively worth. >> >> We would love to have PRs and for us this is great if you do them and not an IA so that we can control the copyright concerns. >> >> So thank you for your time and idea. >> Guille may contact you directly. >> >> S (this week we have 3 working days) and next week we have also some non-working days. >> The month of may is a gruyere. >> >> >>> On 12 May 2026, at 09:10, Aaron Wohl via Pharo-dev <pharo-dev(a)lists.pharo.org> wrote: >>> >>> I regularly have Claude.AI review my code https://awohl.com, I pointed Claude at the Pharo-VM to see what it could see. A lot of the issues it found are things like strcpy without bounds checks with strings no one would ever make that big. However, it found some issues that are always triggered. >>> >>> Full list of issues >>> https://github.com/avwohl/iospharo/blob/main/docs/pharo-vm-code-reivew-2026… >>> >>> I did not make an AI-generated patch list. stephane.ducasse(a)free.fr mentioned copyright concerns by guillermo.polito(a)inria.fr of accepting AI code. I assume this is due to the inability to copyright AI-generated work and to AI's tendency to steal others' work and lie about its origins. However, a lot of the fixes are so trivial, like off-by-one errors, that I don't know how much of an issue it is. If you want me to PR fixes and or tests that trigger for the full list, or always list, let me know. >>> >>> Many of the issues would only happen if someone were trying to break things (MAXLEN symlinks, damaged image files). If one were a mindset, it could be called AI slop. However, here is a short list of things that always cause issues in everyday operation: for example, every plugin loaded damages heap memory, or the nightly build of signed code disables SSL checks, so a simple DNS hack could get malicious code signed. >>> >>> Source: ~/pharo.md (review of /Users/wohl/esrc/pharo-vm @ pharo-10, 2026-05-11) >>> Filter: only items that fire in normal benign operation, not edge cases >>> requiring huge/crafted strings or attacker-chosen sizes. >>> >>> ================================================================ >>> A. ALWAYS â MEMORY DAMAGE / UNDEFINED BEHAVIOR >>> ================================================================ >>> >>> 1. sqNamedPrims.c:56-57 â calloc(sizeof(ModuleEntry)+strlen(name)) then strcpy writes strlen+1; 1-byte heap overflow on every plugin load. [#3.26] >>> 2. ffi/callbacks/callbacks.c:14-32 â stack-allocated CallbackInvocation registered in runner->callbackStack/global queue; sig_longjmp exit leaves dangling stack pointer after every same-thread callback. [#2.8] >>> 3. ffi/typesPrimitives.c:174-188 â setHandler(receiver, structType) stores pointer before failed()/ffi_get_struct_offsets checks; any error path frees memory while receiver still holds the dangling handle. [#2.6] >>> 4. threadSafeQueue.c:113-137 â queue->first and node->element read outside the mutex; lock-holder's free(node) leaves the other consumer walking freed memory on every concurrent dequeue (hit by every FFI workload). [#3.21] >>> 5. SocketPluginImpl.c:1109-1123 â sqSocketDestroy frees PSP(s) after sqSocketAbortConnection queues a closeHandler against pss; AIO dispatch fires on freed memory. [#3.22] >>> 6. ffi/utils.c:43-50 â readString returns an un-pinned image-memory pointer; GC between strlen() and the caller's strcpy invalidates the length and the address. [#5.27] >>> 7. ffi/callbacks/callbacks.c:24-29 â runner->callbackStack chain updated without any lock; reentrant callbacks from multiple threads on the same Runner corrupt the linked list. [#5.4] >>> 8. pathUtilities.c:233-237 â strrchr(name,'.') result stored in fileExtension, but the NULL guard tests the unrelated `extension` variable; strcmp(NULL,...) crashes on any directory entry without a dot (e.g. "Makefile"). [#4.2] >>> 9. pathUtilities.c:163 â first[strlen(first)-1] reads first[-1] (one byte before the buffer) whenever first is "", reachable from parameters.c:210-212 fallback. [#4.3] >>> 10. externalPrimitives.c:57,66 â module path assembled in a file-static moduleNameBuffer with no lock; concurrent loads scribble each other's path and dlopen/LoadLibrary sees a torn string. [#5.3] >>> 11. debugUnix.c:88-95,122-162 â SIGSEGV/SIGBUS/SIGFPE handler calls fopen/vfprintf/backtrace_symbols_fd/ctime_r/semaphore_wait (none async-signal-safe) and uses SA_NODEFER so the handler can re-enter itself on every crash. [#5.1] >>> 12. debugUnix.c:123,144,154 â sigaction.sa_mask never initialized via sigemptyset for term_handler_action and sigpipe_handler_action; kernel reads uninitialized stack to decide what to mask on every install. [#5.2] >>> 13. debug.c:57-66 â glibc strerror_r returns a pointer that may not write to the supplied buffer; caller prints the buffer unconditionally, leaking uninitialized stack bytes on every error path. [#5.7] >>> 14. SocketPluginImpl.c:2494-2496 â sqSocket lastError stored in a file-static, clobbered across sockets; every concurrent socket failure overwrites another socket's error state. [#5.17] >>> 15. aioWin.c:457/465 â heap-interior alias into allHandles transiently equals a freshly malloc'd region; any early return between the two assignments leaves a free-of-interior or double-use hazard. [#1/Â§9 PARTIAL] >>> >>> >>> ================================================================ >>> B. ALWAYS â SECURITY / CORRECTNESS (NOT MEMORY DAMAGE) >>> ================================================================ >>> >>> TLS / SqueakSSL >>> --------------- >>> 1. sqUnixSSL.c:89-143 â SSL_CTX_set_verify never called; SSL_get_verify_result returns X509_V_OK by default â no certificate validation on any TLS connection. [#2.9] >>> 2. sqUnixSSL.c:102-107 â SSLv23_method with only SSLv2/v3 disabled; TLS 1.0 and 1.1 still accepted on every handshake. [#2.9 / #6.3] >>> 3. sqUnixSSL.c:115 â cipher list "!ADH:HIGH:MEDIUM:@STRENGTH" permits MEDIUM ciphers. [#2.9] >>> 4. sqUnixSSL.c:107 â no SSL_OP_NO_COMPRESSION (CRIME), no SSL_OP_NO_RENEGOTIATION, no SSL_OP_CIPHER_SERVER_PREFERENCE. [#6.3] >>> 5. sqWin32SSL.c:269-275,215,349-353 â sqExtractPeerName copies serverName verbatim into peerName instead of extracting the cert subject; epp.pwszServerName=NULL disables SChannel's hostname check, so image-side peerName==serverName is meaningless on every connection. [#3.19] >>> 6. sqMacSSL.c:154-201,262-272,363-383 â kSSLSessionOptionBreakOnServerAuth disables auto verification; manual SecTrustEvaluate runs with no SSL policy carrying the hostname, so hostname is never checked. [#3.20] >>> 7. sqWin32SSL.c:216-218 â SP_PROT_TLS1_0/1_1/1_2 enabled for both client and server roles. [#6.1] >>> 8. sqMacSSL.c:154-164 â SSLSetProtocolVersionMin(ctx, kTLSProtocol1) sets minimum to TLS 1.0. [#6.2] >>> >>> VM internals >>> ------------ >>> 9. memoryUnix.c:66-89,109-111 â JIT pages mmap'd PROT_READ|PROT_WRITE|PROT_EXEC permanently; sqMakeMemoryExecutableFromTo / NotExecutable hooks are commented out, so W^X is defeated on Linux/FreeBSD. [#5.24] >>> 10. debug.c:45 â error(char*) forwards the argument as the format string into the vfprintf-style logger; exported API contract leaks a %n/%s primitive to any future caller-controlled string. [#4.10] >>> 11. ffi/typesPrimitives.c:170-172 â getHandler() returns the first slot of any oop with no class tag check; libffi consumes attacker-shaped ffi_type fields on every struct cif build, giving a controlled-dispatch primitive to anyone who can register an FFI struct. [#2.5] >>> >>> Build / supply chain (every build / every CI run) >>> ------------------------------------------------- >>> 12. Jenkinsfile:84,249 â fetch-and-execute installer via `wget â¦ | bash` over plain HTTP. [#7] >>> 13. scripts/runTests.sh:31 â `wget -O - https://get.pharo.org/64/80 | bash`, executed from PR workflows. [#7] >>> 14. scripts/installCygwin.ps1:7-9 â Cygwin installer + mirror retrieved over plain HTTP. [#7] >>> 15. cmake/importLibFFI.cmake / importLibGit2.cmake / importSDL2.cmake â dependencies pinned to mutable git tags, no commit-SHA. [#7] >>> 16. macros.cmake:69-103 + every cmake/import*.cmake using files.pharo.org â DownloadProject calls omit URL_HASH for libgit2, libssh2, openssl, zlib, SDL2, cairo, pixman, libpng, freetype, fontconfig, harfbuzz, gcc-runtime. [#7] >>> 17. cmake/importFreetype2.cmake:47-49 â direct savannah.gnu.org download with no URL_HASH. [#7] >>> 18. docker/ubuntu-arm64/Dockerfile, docker/debian10-armv7/Dockerfile â base images unpinned (no @sha256 digest). [#7] >>> 19. Jenkinsfile:97-403 â every upload uses `scp -o StrictHostKeyChecking=no` against files.pharo.org. [#7] >>> 20. Jenkinsfile:138 + cmake/sign.cmake:8-11 â SIGN_CERT_PASSWORD passed through environment under a broad withCredentials() block. [#7] >>> 21. .github/workflows/continuous-integration-workflow.yaml:2 â `on: [push, pull_request]` with no `permissions:` block; fork PRs can edit runTests.sh and execute with the workflow GITHUB_TOKEN scope. [#7] >>> 22. .github/workflows/...:11,14,68 â EOL runners (ubuntu-18.04, windows-2016) and EOL actions (checkout@v1, upload-artifact@v1). [#7] >>> 23. cmake/packaging.cmake:92 â CPACK_PACKAGE_CHECKSUM "SHA1". [#7] >>> 24. scripts/installCygwin.ps1:35-48 â `cygwin -q` suppresses signature warnings during install. [#7] >>> 25. CMakeLists.txt:206,266-296 + cmake/Linux.cmake:1 â no -D_FORTIFY_SOURCE=2, no -fstack-protector-strong, no -fPIE/-pie, no -Wformat-security, no -Wl,-z,relro / -z,now / -z,noexecstack on Linux release builds. [#7] >>> 26. CMakeLists.txt:206,266-296 â -Wno-int-conversion and -Wno-pointer-sign actively silenced; both classes of warning catch real bugs. [#7] >>> 27. cmake/Linux.cmake:1 â Linux rpath set to "." (relative to CWD) instead of "$ORIGIN". [#7] >>> 28. CMakeLists.txt:206 â Windows/Cygwin builds lack /GS, /guard:cf, /DYNAMICBASE, /NXCOMPAT. [#7]

May 14, 2026

Re: claude.ai code review of pharo-v

by Sven Van Caekenberghe

https://docs.kernel.org/process/coding-assistants.html It is great that you did this and important. But each change has to be validated by a capable VM developer, who takes responsibility. > On 14 May 2026, at 04:42, Aaron Wohl via Pharo-dev <pharo-dev(a)lists.pharo.org> wrote: > > It has been in the news that Anthropic delayed the release of Mythos to invite groups to fix the AI's bugs. The news reports suggest that the big open-source projects are accepting AI bug fixes (not just bug reports). If the linux kernal and chrome are accepting AI code how can they do it and pharo can not? > https://www.linuxfoundation.org/blog/project-glasswing-gives-maintainers-ad… > I am not suggesting that AI code should be blindly accepted, some of AI bugs and fixes are fine. It is faster to have a human review than to generate fixes. > > ----- Original message ----- > From: stephane ducasse <stephane.ducasse(a)inria.fr> > To: Aaron Wohl <xphu(a)awohl.com> > Cc: guillermo.polito(a)inria.fr, Pharo-dev <pharo-dev(a)lists.pharo.org> > Subject: Re: [Pharo-dev] claude.ai code review of pharo-v > Date: Wednesday, May 13, 2026 3:26 PM > > thanks we will check this. > > >> On 13 May 2026, at 19:24, Aaron Wohl <xphu(a)awohl.com> wrote: >> >> I had Claude create PRs for the current git main and for the version 12 you asked for. >> I didn't submit them because they are AI-generated. I have no interest in doing manual work that an AI can do. On copyright: if not being able to copyright AI work is the issue, perhaps you could copyright the collection (of source lines)? >> >> For pharo-12 there are 93 bug fixes posted here. >> https://www.awohl.com/pharo-bugs-2026-05-13/ >> >> ----- Original message ----- >> From: stephane ducasse <stephane.ducasse(a)inria.fr> >> To: Aaron Wohl <xphu(a)awohl.com> >> Cc: guillermo.polito(a)inria.fr, Pharo Development List <pharo-dev(a)lists.pharo.org> >> Subject: Re: [Pharo-dev] claude.ai code review of pharo-v >> Date: Wednesday, May 13, 2026 8:14 AM >> >> Hi aaron >> >> Today I discussed with Guille (who was and still a bit sick and under recovery) and did not have the opportunity to discuss with Pablo (who is on vacation) >> >> We are interested in pullrequests that improve the security and code of the VM and pluggins. >> So your analyses are definitively worth. >> >> We would love to have PRs and for us this is great if you do them and not an IA so that we can control the copyright concerns. >> >> So thank you for your time and idea. >> Guille may contact you directly. >> >> S (this week we have 3 working days) and next week we have also some non-working days. >> The month of may is a gruyere. >> >> >>> On 12 May 2026, at 09:10, Aaron Wohl via Pharo-dev <pharo-dev(a)lists.pharo.org> wrote: >>> >>> I regularly have Claude.AI review my code https://awohl.com, I pointed Claude at the Pharo-VM to see what it could see. A lot of the issues it found are things like strcpy without bounds checks with strings no one would ever make that big. However, it found some issues that are always triggered. >>> >>> Full list of issues >>> https://github.com/avwohl/iospharo/blob/main/docs/pharo-vm-code-reivew-2026… >>> >>> I did not make an AI-generated patch list. stephane.ducasse(a)free.fr mentioned copyright concerns by guillermo.polito(a)inria.fr of accepting AI code. I assume this is due to the inability to copyright AI-generated work and to AI's tendency to steal others' work and lie about its origins. However, a lot of the fixes are so trivial, like off-by-one errors, that I don't know how much of an issue it is. If you want me to PR fixes and or tests that trigger for the full list, or always list, let me know. >>> >>> Many of the issues would only happen if someone were trying to break things (MAXLEN symlinks, damaged image files). If one were a mindset, it could be called AI slop. However, here is a short list of things that always cause issues in everyday operation: for example, every plugin loaded damages heap memory, or the nightly build of signed code disables SSL checks, so a simple DNS hack could get malicious code signed. >>> >>> Source: ~/pharo.md (review of /Users/wohl/esrc/pharo-vm @ pharo-10, 2026-05-11) >>> Filter: only items that fire in normal benign operation, not edge cases >>> requiring huge/crafted strings or attacker-chosen sizes. >>> >>> ================================================================ >>> A. ALWAYS â MEMORY DAMAGE / UNDEFINED BEHAVIOR >>> ================================================================ >>> >>> 1. sqNamedPrims.c:56-57 â calloc(sizeof(ModuleEntry)+strlen(name)) then strcpy writes strlen+1; 1-byte heap overflow on every plugin load. [#3.26] >>> 2. ffi/callbacks/callbacks.c:14-32 â stack-allocated CallbackInvocation registered in runner->callbackStack/global queue; sig_longjmp exit leaves dangling stack pointer after every same-thread callback. [#2.8] >>> 3. ffi/typesPrimitives.c:174-188 â setHandler(receiver, structType) stores pointer before failed()/ffi_get_struct_offsets checks; any error path frees memory while receiver still holds the dangling handle. [#2.6] >>> 4. threadSafeQueue.c:113-137 â queue->first and node->element read outside the mutex; lock-holder's free(node) leaves the other consumer walking freed memory on every concurrent dequeue (hit by every FFI workload). [#3.21] >>> 5. SocketPluginImpl.c:1109-1123 â sqSocketDestroy frees PSP(s) after sqSocketAbortConnection queues a closeHandler against pss; AIO dispatch fires on freed memory. [#3.22] >>> 6. ffi/utils.c:43-50 â readString returns an un-pinned image-memory pointer; GC between strlen() and the caller's strcpy invalidates the length and the address. [#5.27] >>> 7. ffi/callbacks/callbacks.c:24-29 â runner->callbackStack chain updated without any lock; reentrant callbacks from multiple threads on the same Runner corrupt the linked list. [#5.4] >>> 8. pathUtilities.c:233-237 â strrchr(name,'.') result stored in fileExtension, but the NULL guard tests the unrelated `extension` variable; strcmp(NULL,...) crashes on any directory entry without a dot (e.g. "Makefile"). [#4.2] >>> 9. pathUtilities.c:163 â first[strlen(first)-1] reads first[-1] (one byte before the buffer) whenever first is "", reachable from parameters.c:210-212 fallback. [#4.3] >>> 10. externalPrimitives.c:57,66 â module path assembled in a file-static moduleNameBuffer with no lock; concurrent loads scribble each other's path and dlopen/LoadLibrary sees a torn string. [#5.3] >>> 11. debugUnix.c:88-95,122-162 â SIGSEGV/SIGBUS/SIGFPE handler calls fopen/vfprintf/backtrace_symbols_fd/ctime_r/semaphore_wait (none async-signal-safe) and uses SA_NODEFER so the handler can re-enter itself on every crash. [#5.1] >>> 12. debugUnix.c:123,144,154 â sigaction.sa_mask never initialized via sigemptyset for term_handler_action and sigpipe_handler_action; kernel reads uninitialized stack to decide what to mask on every install. [#5.2] >>> 13. debug.c:57-66 â glibc strerror_r returns a pointer that may not write to the supplied buffer; caller prints the buffer unconditionally, leaking uninitialized stack bytes on every error path. [#5.7] >>> 14. SocketPluginImpl.c:2494-2496 â sqSocket lastError stored in a file-static, clobbered across sockets; every concurrent socket failure overwrites another socket's error state. [#5.17] >>> 15. aioWin.c:457/465 â heap-interior alias into allHandles transiently equals a freshly malloc'd region; any early return between the two assignments leaves a free-of-interior or double-use hazard. [#1/Â§9 PARTIAL] >>> >>> >>> ================================================================ >>> B. ALWAYS â SECURITY / CORRECTNESS (NOT MEMORY DAMAGE) >>> ================================================================ >>> >>> TLS / SqueakSSL >>> --------------- >>> 1. sqUnixSSL.c:89-143 â SSL_CTX_set_verify never called; SSL_get_verify_result returns X509_V_OK by default â no certificate validation on any TLS connection. [#2.9] >>> 2. sqUnixSSL.c:102-107 â SSLv23_method with only SSLv2/v3 disabled; TLS 1.0 and 1.1 still accepted on every handshake. [#2.9 / #6.3] >>> 3. sqUnixSSL.c:115 â cipher list "!ADH:HIGH:MEDIUM:@STRENGTH" permits MEDIUM ciphers. [#2.9] >>> 4. sqUnixSSL.c:107 â no SSL_OP_NO_COMPRESSION (CRIME), no SSL_OP_NO_RENEGOTIATION, no SSL_OP_CIPHER_SERVER_PREFERENCE. [#6.3] >>> 5. sqWin32SSL.c:269-275,215,349-353 â sqExtractPeerName copies serverName verbatim into peerName instead of extracting the cert subject; epp.pwszServerName=NULL disables SChannel's hostname check, so image-side peerName==serverName is meaningless on every connection. [#3.19] >>> 6. sqMacSSL.c:154-201,262-272,363-383 â kSSLSessionOptionBreakOnServerAuth disables auto verification; manual SecTrustEvaluate runs with no SSL policy carrying the hostname, so hostname is never checked. [#3.20] >>> 7. sqWin32SSL.c:216-218 â SP_PROT_TLS1_0/1_1/1_2 enabled for both client and server roles. [#6.1] >>> 8. sqMacSSL.c:154-164 â SSLSetProtocolVersionMin(ctx, kTLSProtocol1) sets minimum to TLS 1.0. [#6.2] >>> >>> VM internals >>> ------------ >>> 9. memoryUnix.c:66-89,109-111 â JIT pages mmap'd PROT_READ|PROT_WRITE|PROT_EXEC permanently; sqMakeMemoryExecutableFromTo / NotExecutable hooks are commented out, so W^X is defeated on Linux/FreeBSD. [#5.24] >>> 10. debug.c:45 â error(char*) forwards the argument as the format string into the vfprintf-style logger; exported API contract leaks a %n/%s primitive to any future caller-controlled string. [#4.10] >>> 11. ffi/typesPrimitives.c:170-172 â getHandler() returns the first slot of any oop with no class tag check; libffi consumes attacker-shaped ffi_type fields on every struct cif build, giving a controlled-dispatch primitive to anyone who can register an FFI struct. [#2.5] >>> >>> Build / supply chain (every build / every CI run) >>> ------------------------------------------------- >>> 12. Jenkinsfile:84,249 â fetch-and-execute installer via `wget â¦ | bash` over plain HTTP. [#7] >>> 13. scripts/runTests.sh:31 â `wget -O - https://get.pharo.org/64/80 | bash`, executed from PR workflows. [#7] >>> 14. scripts/installCygwin.ps1:7-9 â Cygwin installer + mirror retrieved over plain HTTP. [#7] >>> 15. cmake/importLibFFI.cmake / importLibGit2.cmake / importSDL2.cmake â dependencies pinned to mutable git tags, no commit-SHA. [#7] >>> 16. macros.cmake:69-103 + every cmake/import*.cmake using files.pharo.org â DownloadProject calls omit URL_HASH for libgit2, libssh2, openssl, zlib, SDL2, cairo, pixman, libpng, freetype, fontconfig, harfbuzz, gcc-runtime. [#7] >>> 17. cmake/importFreetype2.cmake:47-49 â direct savannah.gnu.org download with no URL_HASH. [#7] >>> 18. docker/ubuntu-arm64/Dockerfile, docker/debian10-armv7/Dockerfile â base images unpinned (no @sha256 digest). [#7] >>> 19. Jenkinsfile:97-403 â every upload uses `scp -o StrictHostKeyChecking=no` against files.pharo.org. [#7] >>> 20. Jenkinsfile:138 + cmake/sign.cmake:8-11 â SIGN_CERT_PASSWORD passed through environment under a broad withCredentials() block. [#7] >>> 21. .github/workflows/continuous-integration-workflow.yaml:2 â `on: [push, pull_request]` with no `permissions:` block; fork PRs can edit runTests.sh and execute with the workflow GITHUB_TOKEN scope. [#7] >>> 22. .github/workflows/...:11,14,68 â EOL runners (ubuntu-18.04, windows-2016) and EOL actions (checkout@v1, upload-artifact@v1). [#7] >>> 23. cmake/packaging.cmake:92 â CPACK_PACKAGE_CHECKSUM "SHA1". [#7] >>> 24. scripts/installCygwin.ps1:35-48 â `cygwin -q` suppresses signature warnings during install. [#7] >>> 25. CMakeLists.txt:206,266-296 + cmake/Linux.cmake:1 â no -D_FORTIFY_SOURCE=2, no -fstack-protector-strong, no -fPIE/-pie, no -Wformat-security, no -Wl,-z,relro / -z,now / -z,noexecstack on Linux release builds. [#7] >>> 26. CMakeLists.txt:206,266-296 â -Wno-int-conversion and -Wno-pointer-sign actively silenced; both classes of warning catch real bugs. [#7] >>> 27. cmake/Linux.cmake:1 â Linux rpath set to "." (relative to CWD) instead of "$ORIGIN". [#7] >>> 28. CMakeLists.txt:206 â Windows/Cygwin builds lack /GS, /guard:cf, /DYNAMICBASE, /NXCOMPAT. [#7] >>

May 14, 2026