Frederik Carlier
Frederik Carlier
It looks somewhat similar to this: https://lists.gnu.org/archive/html/discuss-gnustep/2017-12/msg00083.html / https://lists.gnu.org/archive/html/discuss-gnustep/2017-12/msg00110.html: >>> The `[NSException raise]` method just calls `@throw self` when >>> `_NATIVE_OBJC_EXCEPTIONS` is defined >> >> It does, but `[NSException raise]`...
Just leaving some notes here: This issue looks very similar to the issue which was reported in 2017. The small repro can be used to reproduce the issue, and re-throwing...
@davidchisnall I've verified locally that this is because the vectored exception handler which is used on mingw64 gets invoked for (certain?) exceptions which would be caught by the normal application...
@rfm This was fixed via https://github.com/gnustep/libobjc2/pull/278, which has been backported to the version of libobjc2 which is in MinGW. The remaining CI failure is, I believe, unrelated and being tracked...
For this build: https://github.com/gnustep/libs-base/actions/runs/7890397845/job/21532477606, a slightly different set of tests failed: ``` Running base/NSURL/test01.m... 2024-02-13 17:47:49.222 test01[5456:6932] Unable to map timezone 'Coordinated Universal Time' to IANA format 2024-02-13 17:47:49.222 test01[5456:6932]...
Also, looks like these tests started consistently failing after https://github.com/gnustep/libs-base/commit/d6bb6deff602ec23cf8bc35ba7c53a1fd8275f30, which has the following comment: "Source/NSString.m: Return empty string of correct class when loading from an empty file or URL."
This seems to be pretty consistent now on win64/clang+msvc, causing CI to be red. I propose skipping the failing tests/marking them as hopeful in #398. I believe it's a reasonable...
Are you targeting a specific date for the 1.30.0 release? The latest release is ~1 year old at this point in time.
That's great to hear, thanks!
This would be a very useful feature to have. We allow users to specify option values on the command line, as environment variables (e.g. `MY_OPTION_NAME=foo`), or as files (e.g. `/etc/product/my_option_name`...