Re: Re: tools-windows-msvc runtime error

2023-07-30 Thread loserist
Hi all! Thanks to all those who helped me, those problems I had before have been solved. Frederik, specially, who helped me from the beginning to the end. I am also happy to help those who had the same problem and could not solve it. The last thing I want to say is that I'm an illiterate

Re: tools-windows-msvc runtime error

2023-07-18 Thread David Chisnall
Did you remember to disable incremental linking? Last time I tested it, LINK.EXE did work, but if you had incremental linking enabled (I think it’s on by default?) then it inserts random padding into the Objective-C runtime’s metadata sections, which corrupt various things. David > On 18 Jul

Re: tools-windows-msvc runtime error

2023-07-18 Thread Frederik Seiffert
I tried adding /INCREMENTAL:NO, but the issue persists. Also the documentation says that incremental linking is disabled when the output file doesn’t exist, which is confirmed by this log after deleting the .exe: > LINK : test.exe not found or not built by the last incremental link; >

Re: Re: tools-windows-msvc runtime error

2023-07-18 Thread loserist
David, you hit the nail on the head and your words have inspired me! > > it inserts random padding into the Objective-C runtime’s metadata sections, > which corrupt various things... > Loserist > Did you remember to disable incremental linking? > > Last time I tested it, LINK.EXE did work,

Re: Re: tools-windows-msvc runtime error

2023-07-18 Thread loserist
David, you hit the nail on the head and your words have inspired me! > > it inserts random padding into the Objective-C runtime’s metadata sections, > which corrupt various things... > Loserist > Did you remember to disable incremental linking? > > Last time I tested it, LINK.EXE did work,

Re: Re: tools-windows-msvc runtime error

2023-07-18 Thread loserist
Alright. win10 => 19044 clang version => 16.0.0 gnustep-*, libobjc2, etc.. => https://github.com/gnustep/tools-windows-msvc Thanks again. > I am no Windows expert but I remember that for some compilers we needed > special symbol handling there. We use the macro GS_EXPORT_CLASS there which >

Re: tools-windows-msvc runtime error

2023-07-18 Thread Frederik Seiffert
Thanks, I reproduced the issue here. It turns out using the Microsoft linker causes this issue, but using LLD works fine. I’m not sure why or since when this is, as using link.exe definitely worked for me at one point, but now using either VS 2019 or 2022 causes this crash as soon as

Re: tools-windows-msvc runtime error

2023-07-18 Thread Fred Kiefer
I am no Windows expert but I remember that for some compilers we needed special symbol handling there. We use the macro GS_EXPORT_CLASS there which boils down to some __declspec(dllexport) declarations on classes. Not sure whether this would also be needed for a class that is only locally used.

Re: Re: tools-windows-msvc runtime error

2023-07-17 Thread loserist
Sure! The following is it: * thread #1, stop reason = Exception 0xc005 encountered at address 0x7ffcec4e1048: Access violation reading locatio n 0x * frame #0: 0x7ffcec4e1048 objc.dll`objc_msgSend + 40 frame #1: 0x7ff645cc1154 abc.exe frame #2: 0x7ff645cc142c abc.exe

Re: tools-windows-msvc runtime error

2023-07-17 Thread Frederik Seiffert
Can you send the backtrace of the crash ("bt" in LLDB)? > Am 16.07.2023 um 15:23 schrieb loserist : > > Hi all! I seem to have found the problem.the problem is that the user-defined > class is not working properly, see the following code and its output message > please.Does anyone know how to

Fw: Re: Re: tools-windows-msvc runtime error

2023-07-16 Thread loserist
Hi all! I seem to have found the problem.the problem is that the user-defined class is not working properly, see the following code and its output message please.Does anyone know how to fix this? | #import @interface SayHello : NSObject - (void)greet; @end @implementation SayHello -

tools-windows-msvc runtime error

2023-07-15 Thread loserist
I know this is an error usually caused by null pointers, but my code has been tested to be fine under linux. When I compile and run my program on windows using tools-windows-msvc provided by gnustep, I get this error, and I suspect that it is caused by one of gnustep's own libraries on windows,

Re: tools-windows-msvc runtime error

2023-07-15 Thread H. Nikolaus Schaller
Just a note > Am 15.07.2023 um 17:27 schrieb M A : > >NSString *mystring; // nil pointer this is not a nil pointer but an uninitialized variable. Try: NSString *mystring = nil; // nil pointer Nevertheless it could be the reason why "loserist" sees his exception,

Re: tools-windows-msvc runtime error

2023-07-15 Thread M A
My guess is a nil pointer was accessed. I made this test program to see what would happen if a nil pointer was accessed: #include int main(int argc, char *argv[]) { NSString *mystring;// nil pointer NSLog(@"mystring: %@", mystring); // crash here } The result was

tools-windows-msvc runtime error

2023-07-15 Thread loserist
Hi all! I want to get help from you.Thank You. | C:\>echo %errorlevel% -1073741819 (lldb) Process 3708 launched: 'C:\a.exe' (x86_64) Process 3708 stopped * thread #1, stop reason = Exception 0xc005 encountered at address 0x7ffb37a81048: Access violation reading locatio n 0x