Re: MacPorts vs. Apple compiler issues, Handle

Riccardo Mottola via macports-users Mon, 18 Mar 2024 04:51:15 -0700

Hi Joshua,

Joshua Root wrote:

Yes, any number of programs have had bugs that only became apparentwhen building with a newer compiler. But that's a very broad category,so without knowing the nature of the crash you're seeing, it'simpossible to say what else might have had a similar problem.

I imagined that, but perhaps somebody experienced like a recurring issue!

On FreeBSD I compile with clang 12 and it works, so they issue could beApple specific, either in the Apple code part or in dependent SDK andlibraries.

Bugs in clang are not unknown, but far more common is programs relyingon certain behaviour for operations that have undefined behaviouraccording to the language standard. Or sometimes the layout of memoryjust shifts slightly, causing a previously benign buffer overflow todo damage. Sometimes a newer compiler will also default to a newerversion of the language, so if that's the cause of the differingbehaviour, you can use -std to change it back.

I did try clang 10 and it compiles, but crashes. So probably it is not acompiler bug (although sometimes the remain undetected for years...).

I will do another compilation reducing the optimization level. GCC hasan issue where beyond gcc6 certain optimizations need to be disabled, orAF crashes.

Otherwise, you have to do the hard work of debugging: Look at thecrash report to see where and how the code is crashing, pay attentionto compiler warnings, and systematically eliminate possibilities ofwhat could be going wrong. Building with clang's sanitizers may behelpful, particularly -fsanitize=address and -fsanitize=undefined,though in a code base this size I wouldn't be surprised if they alsodetected hundreds of other potential issues.


Indeed, it is a big code base, with hundreds of warnings...

I don't get very smart on the crash report either. Where is the issue? Idon't see a trace and don't know how to read it. Sorry to admit that!


Process:               arcticfox [93365]
Path: /Users/USER/Documents/*/ArcticFox.app/Contents/MacOS/arcticfox
Identifier:            org.mozilla.arctic fox
Version:               44.0 (4424.3.18)
Code Type:             X86-64 (Native)
Parent Process:        Python [93301]
Responsible:           arcticfox [93365]
User ID:               501

Date/Time:             2024-03-18 11:52:05.968 +0100
OS Version:            Mac OS X 10.13.6 (17G14042)
Report Version:        12
Anonymous UUID:        195FD101-66EF-B75D-42D8-012488A629B7


Time Awake Since Boot: 49000 seconds

System Integrity Protection: disabled

Crashed Thread:        0  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       KERN_INVALID_ADDRESS at 0x00007ffe00002007
Exception Note:        EXC_CORPSE_NOTIFY

Termination Signal:    Segmentation fault: 11
Termination Reason:    Namespace SIGNAL, Code 0xb
Terminating Process:   exc handler [0]

VM Regions Near 0x7ffe00002007:

Stack 0000700005310000-0000700005392000 [ 520K]rw-/rwx SM=COW thread 29

-->

MALLOC_TINY 00007ffe25c00000-00007ffe26000000 [ 4096K]rw-/rwx SM=PRV


Thread 0 Crashed:: Dispatch queue: com.apple.main-thread

0 XUL 0x000000010f5468e1nsWindowWatcher::OpenWindowInternal(mozIDOMWindowProxy*, char const*,char const*, char const*, bool, bool, bool, nsITabParent*, nsIArray*,nsIDocShellLoadInfo*, mozIDOMWindowProxy**) + 273


Thread 1:

0 libsystem_kernel.dylib 0x00007fff50c8728a__workq_kernreturn + 101 libsystem_pthread.dylib 0x00007fff50e4e20e_pthread_wqthread + 1552

2   libsystem_pthread.dylib           0x00007fff50e4dbe9 start_wqthread + 13

Thread 2:

0 libsystem_kernel.dylib 0x00007fff50c8728a__workq_kernreturn + 101 libsystem_pthread.dylib 0x00007fff50e4e009_pthread_wqthread + 1035

2   libsystem_pthread.dylib           0x00007fff50e4dbe9 start_wqthread + 13

Thread 3:

0 libsystem_kernel.dylib 0x00007fff50c8728a__workq_kernreturn + 101 libsystem_pthread.dylib 0x00007fff50e4e20e_pthread_wqthread + 1552

2   libsystem_pthread.dylib           0x00007fff50e4dbe9 start_wqthread + 13

Thread 4:

0 libsystem_kernel.dylib 0x00007fff50c8728a__workq_kernreturn + 101 libsystem_pthread.dylib 0x00007fff50e4e20e_pthread_wqthread + 1552

2   libsystem_pthread.dylib           0x00007fff50e4dbe9 start_wqthread + 13

Thread 5:

0 libsystem_kernel.dylib 0x00007fff50c8728a__workq_kernreturn + 101 libsystem_pthread.dylib 0x00007fff50e4e009_pthread_wqthread + 1035

2   libsystem_pthread.dylib           0x00007fff50e4dbe9 start_wqthread + 13

Thread 6:: Gecko_IOThread
0   libsystem_kernel.dylib            0x00007fff50c87bea kevent + 10
1   XUL                               0x000000010da95bff kq_dispatch + 687

Thread 7:: Socket Thread
0   libsystem_kernel.dylib            0x00007fff50c86cf2 __select + 10
1   libnss3.dylib                     0x000000010d5ee576 poll + 470

Thread 8:: JS Watchdog

0 libsystem_kernel.dylib 0x00007fff50c86a16 __psynch_cvwait+ 101 libsystem_pthread.dylib 0x00007fff50e4f589_pthread_cond_wait + 732


Thread 9:: JS Helper