Re: libobjc2 still failing tests

./conftest$ac_exeext configure:7884: $? = 139 configure: program exited with status 139 configure: failed program was: | /* confdefs.h */ > On 26 Jan 2019, at 17:35, David Chisnall wrote: > > On 26 Jan 2019, at 15:59, Andreas Fink wrote: >> >> I can reproduce the same problem

Re: libobjc2 still failing tests

+ foundation so my stuff can build on top properly. The older version I use currently seems to not release memory in some cases and out of a sudden my apps eat gigabytes of ram for nothing (and its not my objects not being deallocated. I verified this) > On 26 Jan 2019, at 13:21, Andreas Fink wr

Re: libobjc2 still failing tests

19, at 11:57, Andreas Fink wrote: >> >> * thread #1, name = 'basictypes', stop reason = signal SIGSEGV: invalid >> address (fault address: 0x7f7feffc) >> * frame #0: 0x76a22d4e libc.so.6`_IO_vfprintf + 30 >> frame #1: 0x76a4be89

Re: libobjc2 still failing tests

> On 26 Jan 2019, at 12:48, David Chisnall wrote: > > On 26 Jan 2019, at 11:35, Andreas Fink wrote: >> >> ok removing the static in the test fixes the test. >> But when I try to use it from gnustep-base, all tests are failing there. > > I was seeing an i

Re: libobjc2 still failing tests

ts not a building issue but a runtime crash of a simple test which is totally confusing.. > On 25 Jan 2019, at 18:07, David Chisnall wrote: > > On 25/01/2019 16:46, Andreas Fink wrote: >> 17/162 Test #17: AssociatedObject .. >

Re: libobjc2 still failing tests

vid Chisnall wrote: > > On 25/01/2019 14:01, Andreas Fink wrote: >> I found out what makes it break. >> The cmake option -DCMAKE_BUILD_TYPE=RelWithDebInfo > > Thanks. There was a bug in the log2 calculation for storing the ivar offsets > that worked at O0 because

Re: libobjc2 still failing tests

, David Chisnall wrote: > > On 25/01/2019 11:35, Andreas Fink wrote: >> With clang-7 I get these test results >> 96% tests passed, 6 tests failed out of 162 >> Total Test time (real) = 23.69 sec >> The following tests FAILED: >>7 - alignTest_le

Re: libobjc2 still failing tests

9, at 14:19, David Chisnall wrote: > > On 25/01/2019 11:35, Andreas Fink wrote: >> With clang-7 I get these test results >> 96% tests passed, 6 tests failed out of 162 >> Total Test time (real) = 23.69 sec >> The following tests FAILED: >>7 - alignTes

Re: libobjc2 still failing tests

) 36 - ConstantString_legacy_optimised (OTHER_FAULT) 123 - zeroSizedIVar_legacy (OTHER_FAULT) 124 - zeroSizedIVar_legacy_optimised (OTHER_FAULT) Errors while running CTest Makefile:83: recipe for target 'test' failed > On 25 Jan 2019, at 12:28, Andreas Fink wr

Re: libobjc2 still failing tests

t; > Total Test time (real) = 5.09 sec > > I can only fix bugs that I can reproduce. > > David > > On 25/01/2019 09:43, Andreas Fink wrote: >> How can these tests be fixed? >> (or are there non fatal as there is always another version which works?) >> 95

libobjc2 still failing tests

How can these tests be fixed? (or are there non fatal as there is always another version which works?) 95% tests passed, 8 tests failed out of 162 Total Test time (real) = 24.94 sec The following tests FAILED: 7 - alignTest_legacy (OTHER_FAULT) 8 -

Re: GNUStep runtime / libobjc2 build problems: tests failing or segfaulting

> On 16 Jan 2019, at 15:37, David Chisnall wrote: > > On 16/01/2019 10:40, Andreas Fink wrote: >> cd libobjc2 >> mkdir Build >> cd Build >> cmake .. -DCMAKE_BUILD_TYPE=RelWithDebInfo -DBUILD_STATIC_LIBOBJC=1 >> -DCMAKE_C_COMPILER=${CC} -DCMAKE_CXX_

Re: GNUStep runtime / libobjc2 build problems: tests failing or segfaulting

en installed. I can give access to that system if needed. I only created this VM for testing this specific case. > On Tue, Dec 18, 2018 at 9:31 AM Andreas Fink <mailto:af...@list.fink.org>> wrote: > Hi all, > > I'm trying to build gnustep base with clang-7 on deb

Re: Some GNUstep discussions in other forums

> On 27 Dec 2018, at 12:56, H. Nikolaus Schaller wrote: > > Hi David, > >> Am 27.12.2018 um 12:15 schrieb David Chisnall : >> >> On 26/12/2018 16:08, Patryk Laurent wrote: >>> Hi David, a language (which is somewhat dated even in its latest incarnation). >>> I would love to know your

libobjc ABI incompatibilities

Hello all I have a project constantly eating memory in some cases. With the help of Valgind I broke it down to the fact that apparently all objc objects are never released and this not in my code and it seems to be they are all allocated like this: ==26443== 4,825,344 bytes in 50,264 blocks

Re: does method invocation involve a lock?

If I remember correctly, methods are not locked. They can run in parallel multiple times in multiple threads. The exception are properties with the atomic attribute where the compiler synthesizes the getter/setter and thus makes sure that a getter and setter dont conflict with each other

Re: make fails in gnustep base

The bad thing is that pkg-config puts the order of linking exactly in the order which test2 is in which means the root object is last in the chain. > On 4 Sep 2018, at 08:56, Andreas Fink wrote: > > > Here is a simple test case illustrating the problem > > TestObje

Re: make fails in gnustep base

_int6=99 _int7=99 _string8=6.93489458547e-310 _int9=99 _string10=s1010 > On 4 Sep 2018, at 07:37, Andreas Fink wrote: > > > >> On 3 Sep 2018, at 23:40, Ivan Vučica wrote: >> >> So, uh, libulibtcap depends on code in libasn1? Library order matters >>

Re: make fails in gnustep base

> On 3 Sep 2018, at 23:40, Ivan Vučica wrote: > > So, uh, libulibtcap depends on code in libasn1? Library order matters > to the linker. Sure thats why we have linkers. it dynamically links things together. These are all dynamic libraries so the final linking should find all references or

Re: make fails in gnustep base

On 31/08/2018 09:22, Andreas Fink wrote: >> all latest compiled from these sources: > > It looks like someone at Apple broke blocks on all ELF platforms a couple of > weeks ago. It's not been merged to the 7 release branch though, so building > from that should fix

Re: make fails in gnustep base

) 152 - CXXExceptions_optimised (SEGFAULT) 155 - ObjCXXEHInterop (SEGFAULT) 156 - ObjCXXEHInterop_optimised (SEGFAULT) > On 31 Aug 2018, at 10:38, Andreas Fink wrote: > > *facepalm* > > its a constant race between bugfixes and introduction of other bugs on th

Re: make fails in gnustep base

*facepalm* its a constant race between bugfixes and introduction of other bugs on the other side... :) Thanks for the hint, I'll try release 7... > On 31 Aug 2018, at 10:29, David Chisnall wrote: > > On 31/08/2018 09:22, Andreas Fink wrote: >> all latest compiled fro

Re: make fails in gnustep base

block descriptor is including a full type encoding without > mangling it, which doesn't work on most ELF platforms because the @ symbol is > used as a separator between symbol name and version. > > David > > On 30/08/2018 22:22, Andreas Fink wrote: >> anyone having a h

make fails in gnustep base

anyone having a hint where this is coming from: [root@localhost base]# make install This is gnustep-make 2.7.0. Type 'make print-gnustep-make-help' for help. Running in gnustep-make version 2 strict mode. Making all in Source ... Making all in Additions ... Making all for subproject Additions...

Re: building GNUstep from scratch

I had good success with libojbc/clang under debian9 (stretch). I wouldn't want to go back to gcc due to non support of certain stuff I use every day (the stuff which apple introduced in what they called objc2.0). Part is working in recent gcc's though but I like clangs error reporting and

libobjc2 broken in current git

The current git version of libobjc2 seems broken The version I used before (commit 14889c540fe7da84080aaa87342df40e0a7091e7) worked. The current one spills out a lot of undefined header stuff for example in extern struct objc_slot_v1 *objc_get_slot(Class, SEL) OBJC_NONPORTABLE

Re: libobjc2 broken in current git

> On 22 May 2018, at 09:45, Andreas Fink <af...@list.fink.org> wrote: > > The current git version of libobjc2 seems broken > > The version I used before (commit 14889c540fe7da84080aaa87342df40e0a7091e7) > worked. > The current one spills out a lot of undefined hea

Re: signal SIGSEGV, Segmentation fault

or run the binary with lldb and set a breakpoint at [NSException raise] to catch any exceptions thrown. break set -S raise Once you get the crash, you end up in lldb debugger and can issue "bt" for backtrace and you see exactly where you are. > On 8 May 2018, at 19:35, Fred Kiefer

Re: Linking frameworks does not work

I'm not 100% sure how GNUStep frameworks are supposed to be linked but fact is under linux, it looks for shared libraries in all which is referenced in /etc/ld.so.conf (and /etc/ld.so.conf.d/* ). On the mac the path to a shared library is embedded in the library itself so when you link to it,

Re: Linking frameworks does not work

could it simply be that your /etc/ld.so.conf setup does not include the needed paths to find SRFoundation framework or you didnt run ldconfig after installing/updating the shared library? > On 2 May 2018, at 15:45, Andreas Höschler wrote: > > Hi Wolfgang, > >> On 2.

Windows Project center not working

Hello all, Today I tried to download gnustep for windows to see if it makes sense to port my MacOS / Gnustep Linux app to Windows as well. However I failed at ProjectCenter which simply throws a Windows C++ runtime library error without saying much. This is on a Windows 10 installation with no

Re: Accessing array members without the use of objectAtIndex

nd. If so, what do I need to do to start > using this feature. Else if not, is there a plan to add this in the > (hopefully near) future? > > Thanks, > Tyler McLean > > ___ > Dis

Re: GNUstep and valgrind

> >> How GnuStep has implemented drain vs. release I would have to check. But if >> you follow the Apple documentation, the GnuStep implementation should follow >> along (with a few exceptions which are not implemented [yet]). So calling >> drain would be a safe bet. > > Indeed. It is safer.

Re: GNUstep and valgrind

> On 20 Mar 2018, at 08:22, H. Nikolaus Schaller <h...@goldelico.com> wrote: > > >> Am 20.03.2018 um 08:11 schrieb Andreas Fink <af...@list.fink.org>: >> >> >> You never call "release" on a autorelease pool. > > Not &qu

Re: GNUstep and valgrind

You never call "release" on a autorelease pool. you call "drain" to empty it. NSAutoreleasePool *arp=[[NSAutoreleasePool alloc]init]; ... [arp drain]; would be more or less the same as @autoreleasepool { ... } > On 20 Mar 2018, at 08:08, H. Nikolaus Schaller

Re: Compiling gnustep-make

You need a better compiler for ObjC. If you follow these instructions https://github.com/andreasfink/ulib/blob/master/doc/README-Debian9-stretch.txt it works perfectly ok on Debian 9 using the Debian provided

SIGABRT and SIGV in libobjc2

Hello folks, I have a heavily multithreaded application which produces two different crashes in libobjc2 code now. I believe I have hit a race condition. Here is the firs thread at SIGABRT: * frame #0: 0x76f701be libobjc.so.4.6`objc_storeWeak(addr=0x7fff7be0d628,

Re: NSDecrementExtraRefCountWasZero

> On 3 Dec 2017, at 11:46, David Chisnall wrote: > > On 30 Nov 2017, at 08:52, Richard Frith-Macdonald > wrote: >> >> >> >>> On 29 Nov 2017, at 12:43, David Chisnall >>> wrote: >>> >>> Hello the

Re: libobjc2 & arc & multithreading

I will give it a throughout test the coming days... > On 27 Nov 2017, at 18:33, David Chisnall wrote: > > On 27 Nov 2017, at 09:03, David Chisnall wrote: >> >> The other thing that would probably make a bigger difference is to use a bit >> in the

libobjc2 & arc & multithreading

to join our efforts in this area or has some feedback on this subject? We have not touched libobjc2 code part until now but its essentially our performance bottleneck now. Andreas Fink -- Fink Telecom Services, Paradieshofstrasse 101

<    1   2