gnustep-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Segmentation Faults - OpenBSD


From: David Chisnall
Subject: Re: Segmentation Faults - OpenBSD
Date: Fri, 13 Apr 2018 07:55:04 +0100

On 13 Apr 2018, at 00:31, Riccardo Mottola <address@hidden> wrote:
> 
> Hi,
> 
> Richard just commited some promising fixes.
> 
> Things seem better, but not stable. Here a summary of the current status. 
> OpenBSD seems fine on x86, on amd64 I get some strange issues that might not 
> be related
> 
> FreeBSD/amd64/clang
> - seems to work with all apps I tried
> - One test failure:
> base/NSException/basic.m:
> Failed test:     basic.m:51 ... addresses and symbols match

This test appears to expect the system backtrace_symbols function to demangle 
Objective-C method names.  It should probably be changed to a hope rather than 
an excepted behaviour, because I’ve never seen it pass.

> OpenBSD/i386/gcc
> - seems to work fine
> - Two test failures
> base/NSException/basic.m:
> Failed test:     basic.m:51 ... addresses and symbols match
> base/NSProcessInfo/general.m:
> Failed test:     general.m:48 ... -systemUptime works

This one probably needs some per-platform plumbing.

> 
> 
> OpenBSD/amd64/gcc
> - gui apps do not start due to some symbol relocations maybe a spurious error
> - Two test failures
> base/NSException/basic.m:
> Failed test:     basic.m:50 ... call stac addresses is not empty

You may need to link libexecinfo to make this work on OpenBSD (I think we do 
that by default if it’s found, but maybe it wasn’t installed?)

David


reply via email to

[Prev in Thread] Current Thread [Next in Thread]