Skip to content

Static strings w/o a NSString class produce SIGSEGV #9

@mulle-kybernetik-tv

Description

@mulle-kybernetik-tv
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff7f369f8 in _mulle_atomic_pointer_read (address=0x0)
    at /home/src/srcO/MulleUI/MulleUICaca/test/dependency/include/mulle-thread/mulle-atomic-c11.h:272
272        result = atomic_load_explicit( address, memory_order_relaxed);
(gdb) bt
#0  0x00007ffff7f369f8 in _mulle_atomic_pointer_read (address=0x0)
    at /home/src/srcO/MulleUI/MulleUICaca/test/dependency/include/mulle-thread/mulle-atomic-c11.h:272
#1  _mulle_objc_cachepivot_atomicget_entries (p=0x0) at /home/src/srcO/mulle-objc/mulle-objc-runtime/src/mulle-objc-cache.h:162
#2  mulle_objc_object_call (obj=0x405120 <_unnamed_nsstring>, methodid=174245054, parameter=0x7fffffffd978)
    at /home/src/srcO/mulle-objc/mulle-objc-runtime/src/mulle-objc-call.c:99

Possible idea. There is a global symbol, that is used as the static string class and compiled/linked into the strings. The actual class information with method lists and so forth is then set by the Foundation.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions