You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reported in version: 2.0.10 Reported for operating system, platform: Linux, Other
Comments on the original bug report:
On 2019-12-08 14:41:23 +0000, Paul Cercueil wrote:
Running a basic SDL2 app on a MIPS-based Buildroot system running uClibc or musl (glibc untested) results in SDL_Init() locking up and eating the CPU in the process.
From a quick GDB session on the uClibc-based system, it appears to busy-loop in _dl_find_hash() (uclibc-1.0.32/ldso/ldso/dl-hash.c).
The fact that it happens with both musl and uClibc, and only with SDL2 and no other library or app, makes me think it's a bug of SDL2.
On 2019-12-08 14:54:07 +0000, Ryan C. Gordon wrote:
This function generally means the dynamic loader is resolving symbols. If you observed this under the debugger, can you run the “bt” command and paste the output here? It’s probably going to be somewhere under a dlopen() call.
--ryan.
On 2019-12-08 17:54:12 +0000, Paul Cercueil wrote:
Unfortunately it doesn't go very far:
(gdb) bt
0 0x77e6ab88 in _dl_find_hash () from /lib/ld-uClibc.so.0
1 0x77e6aba4 in _dl_find_hash () from /lib/ld-uClibc.so.0
Backtrace stopped: frame did not save the PC
(and yes, I compiled SDL2 with -ggdb3 and GDB did load the symbols).
On 2019-12-08 18:32:22 +0000, Paul Cercueil wrote:
I added debug to src/loadso/dlopen/SDL_sysloadso.c.
From what I can see, it seems to hang within dlopen(), when libdrm.so.2 is opened for the second time.
This bug report was migrated from our old Bugzilla tracker.
These attachments are available in the static archive:
Reported in version: 2.0.10
Reported for operating system, platform: Linux, Other
Comments on the original bug report:
On 2019-12-08 14:41:23 +0000, Paul Cercueil wrote:
On 2019-12-08 14:54:07 +0000, Ryan C. Gordon wrote:
On 2019-12-08 17:54:12 +0000, Paul Cercueil wrote:
On 2019-12-08 18:32:22 +0000, Paul Cercueil wrote:
On 2019-12-17 22:38:53 +0000, Paul Cercueil wrote:
On 2019-12-17 23:33:44 +0000, Paul Cercueil wrote:
On 2019-12-20 05:48:06 +0000, Sam Lantinga wrote:
The text was updated successfully, but these errors were encountered: