NSProxy failure on Solaris
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 18/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- objective-c
- Domain
- backend
Research direction
The crash is a SIGSEGV in GSMakeFinePoint called from TypeTester finePointPfinePoint: in base/NSProxy/test01.m (around lines 21, 130 and 227), reached through GSFFIInvocation.m and libffi on Solaris. Start by reading the NSProxy test and the FFI invocation path, then build and run test01.m on a Solaris or similar SPARC-based system to reproduce. Done means the test completes without the signal and the NSPoint struct passes through the invocation intact.
Written by the indexing model from the issue text.
Description
base/NSProxy/test01.m:
Failed file: test01.m aborted without running all tests!
Passed test: (2025-11-05 14:47:06.905 GMT+1) test01.m:226 ... Proxy NSPoint
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1 (LWP 1)]
0x00011b34 in GSMakeFinePoint (x=437, y=243) at test01.m:21
21 return point;
(gdb) bt
#0 0x00011b34 in GSMakeFinePoint (x=437, y=243) at test01.m:21
#1 0x000123c8 in -[TypeTester finePointPfinePoint:] (self=0x32248,
_cmd=0x26e70 <_OBJC_SELECTOR_TABLE+352>, v=...) at test01.m:130
#2 0xfebd2ca8 in ffi_call_v8 () from /opt/csw/lib/libffi.so.8
#3 0xfebd22b4 in ffi_call_int () from /opt/csw/lib/libffi.so.8
#4 0xfef5713c in -[GSFFIInvocation invokeWithTarget:] (self=0x18ee70, _cmd=<optimized out>,
anObject=0x32248) at GSFFIInvocation.m:456
#5 0xfee1ecb0 in -[NSInvocation invoke] (self=0x18ee70, _cmd=0x26db8 <_OBJC_SELECTOR_TABLE+168>)
at NSInvocation.m:676
#6 0x000127f4 in -[MyProxy forwardInvocation:] (self=0xaccf0,
_cmd=0xff19c258 <_OBJC_SELECTOR_TABLE+184>, inv=0x18ee70) at test01.m:174
#7 0xfef56714 in GSFFIInvocationCallback (cif=0x18edf8, retp=0xffbff7f0, args=0xffbff698,
user=<optimized out>) at GSFFIInvocation.m:610
#8 0xfebd28f0 in ffi_closure_sparc_inner_v8 () from /opt/csw/lib/libffi.so.8
#9 0xfebe6bac in ffi_closure_v8 () from /opt/csw/lib/libffi.so.8
#10 0x00013cd8 in gnustep_base_user_main (argc=1, argv=0xffbff93c) at test01.m:227
#11 0x00011210 in _start ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
- Dominant language
- Objective-C
- Stars
- 997
- Forks
- 305
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 56
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from gnustep/libs-base
-
Rewrite runloop event polling for simplification/efficiency, implement common modes for eventPossibly taken @rfm claimed this 11 days ago. Openenhancement
gnustep/libs-base#865 · 1 comment · 1 assignee ·
Maintainers usually reply within 2 days
-
Optimise -performSelector:withObject:afterDelay: and -performSelector:withObject:afterDelay:inModes:Openenhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
Maintainers usually reply within 2 days
-
Difficulty 3/5 Half a day Newbie friendliness 45/100
gnustep/libs-base#850 · 5 comments ·
Maintainers usually reply within 2 days
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
Maintainers usually reply within 2 days
-
1.32 release?Open
Difficulty 5/5 Over a week Newbie friendliness 20/100
gnustep/libs-base#784 · 3 comments ·
Maintainers usually reply within 2 days
All issues in gnustep/libs-base
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
[FEATURE REQUEST] Replace "Nothing to see here-yet" text string with "This Tweet has been deleted"Openenhancement
Difficulty 1/5 Under an hour Newbie friendliness 70/100
NeoFreeBird/app#204 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
lynx-family/lynx#10587 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 65/100
SwiftOldDriver/iOS-Weekly#5480 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Hammerspoon/hammerspoon#3913 ·