-
-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Segmentation fault on mediainfo #5124
Comments
I am not able to reproduce the segfault on aarch64 android 10 or arm android 7, so what is your output of |
Well, I'm relieved that at least I didn't break everyone's system 😄 My termux-info output:
At the moment I don't have any other physical device on which to test. I tested using the Android SDK Emulator (system-images;android-29;google_apis;x86_64) and I cannot reproduce the error there either. I would be nice to know if other people with similar devices also get this error. |
I tested again with the emulator image for Android 7.1 (system-images;android-25;google_apis;x86_64) and there I can reproduce the segmentation fault. Running in gdb shows however the error "stack corruption detected" instead of the SIGSEGV when running on the phone. |
Could you install these debug builds: libzen-dbg_0.4.38-1_aarch64.deb, mediainfo-dbg_20.03-1_aarch64.deb and give gdb another shot? |
I get this output with the libzen-dbg, mediainfo-dbg provided:
I'm not really an expert with gdb, I only know about "run" 😕. Is there any option/command that I should use for more verbosity? |
Try |
Thanks for the tip! The results of the backtrace:
The code around line 596 in Ztring.cpp:
The function used in the code is mbsrtowcs and not mbsnrtowcs like showed in the error... Besides, the function mbsrtowcs is also used on line 592 and there is no error there... Does this look more like a Termux/Android specific error or a bug in the ZenLib code? |
Have you tried
before executing mediainfo ? |
Using export LD_PRELOAD=$PREFIX/lib/libandroid-support.so before running does fix the segmentation fault. |
Thanks for the fix! Unfortunately, the segmentation fault persists even with libzen-0.4.38-2. The backtrace message is the same. I have created a patch to explicitly link libandroid-glob in the configure file (like I did for libandroid-glob) and rebuilt libzen again, but the segmentation fault is still there.
|
Hm, weird.. |
- try to add |
Using the tip I have built libzen again using the following patch, but the segmentation fault is still there.
|
This issue/PR has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This comment has been minimized.
This comment has been minimized.
It seems like just a matter of symbol search order by the dynamic linker. Will be worked around by adding FYI, I am now facing a similar issue with |
Note that by default a shared library is not linked against an executable which does not have any reference to symbols defined by the library:
|
I just contributed an update to the packages libzen, libmediainfo and mediainfo. Unfortunately, this update leads to a segmentation fault when running the"mediainfo" command:
The error appears to be caused by the new libzen library, since downgrading to 0.4.37-1 while keeping libmediainfo 20.03-1 and mediainfo 20.03-1 works.
Can the package libzen be rolled back to version 0.4.37-1 until a fix for version 0.4.38 is found?
Thanks and sorry for not testing before opening the pull request.
The text was updated successfully, but these errors were encountered: