ffmpeg - Abort trap 6

[Richard L. Hamilton]

It should have looked something like

sh-3.2$ file /opt/local/lib/libavcodec.58.134.100.dylib
/opt/local/lib/libavcodec.58.134.100.dylib: Mach-O 64-bit dynamically linked shared library x86_64

with parts varying depending on OS version (Mojave or older could be 32-bit) and CPU architecture (Intel  (x86_64 or i386) vs Apple Silicon (arm64).

So the files are damaged (unless you are using a nonstandard version of "file" which doesn't recognize Maco-O binaries), which means re-install the ffmpeg port.

How did the files get damaged?  Let's just say that in the absence of ECC RAM plus some other design choices, a memory error on some Unix implementations could turn a read into a write. I haven't looked at the macOS source code enough to decide how likely that is on macOS. Or user error, or error or malice in any program running with sufficient privileges. Or undetected storage device or filesystem issues. Lots of reasons, in other words.


> On Oct 2, 2024, at 23:27, Michael Newman via macports-users <macports-users at lists.macports.org> wrote:
> 
> Sellotape:bin mnewman$ file /opt/local/lib/libavcodec.58.dylib /opt/local/lib/libavcodec.58.134.100.dylib
> /opt/local/lib/libavcodec.58.dylib:         data
> /opt/local/lib/libavcodec.58.134.100.dylib: data
> 
> Unfortunately, I don’t recall if ffmpeg was built from source or via binary. Sorry.
> 
> This on a 2019 Intel iMac upgraded to Sequoia (15.0) just two days ago.
> 
>> On Oct 3, 2024, at 10:02, Ryan Carsten Schmidt <ryandesign at macports.org> wrote:
>> 
>> On Oct 2, 2024, at 20:50, Michael Newman wrote:
>>> 
>>> Reason: tried: '/opt/local/lib/libavcodec.58.dylib' (not a mach-o file),
>> 
>>> '/opt/local/lib/libavcodec.58.134.100.dylib' (not a mach-o file),
>> 
>> That shouldn't be... What kinds of files are these then—what does this command say?
>> 
>> file /opt/local/lib/libavcodec.58.dylib /opt/local/lib/libavcodec.58.134.100.dylib
>> 
>> Do you recall seeing whether this port built from source on your system or if you received a binary? If you're not sure that's ok. I'll check the archives on our server to see if they have this problem. What macOS version and architecture (arm64 or c86_64) is the machine where you see this problem?
>