I've figured this bug out. It's caused by a design flaw in macOS Big Sur. The problem is that many system files are no located in the OS's file system. Instead they're lumped together in a dynamic linker cache, where `dump_syms` can't find them. Others have already run into this: https://github.com/vispy/vispy/issues/1885 So we're going to have to rewrite `dump_syms` :-( I'll leave this bug open. Then, if nobody else beats me to it, at some point I'll do the required rewrite of `dump_syms`, either here on in another bug.
Bug 1661771 Comment 2 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
I've figured this bug out. It's caused by a design flaw in macOS Big Sur. The problem is that many system files are no located in the OS's file system. Instead they're lumped together in a dynamic linker cache, where `dump_syms` can't find them. Others have already run into this: https://github.com/vispy/vispy/issues/1885 So we're going to have to rewrite `dump_syms` :-( I'll leave this bug open. Then, if nobody else beats me to it, at some point I'll do the required rewrite of `dump_syms`, either here or in another bug.
I've figured this bug out. It's caused by a design flaw in macOS Big Sur. The problem is that many system files are no longer located in the OS's file system. Instead they're lumped together in a dynamic linker cache, where `dump_syms` can't find them. Others have already run into this: https://github.com/vispy/vispy/issues/1885 So we're going to have to rewrite `dump_syms` :-( I'll leave this bug open. Then, if nobody else beats me to it, at some point I'll do the required rewrite of `dump_syms`, either here or in another bug.