Comment # 2
on bug 71543
from Nikolay Amiantov
I've got stack trace: Program received signal SIGSEGV, Segmentation fault. 0x45b2e4a8 in udev_list_entry_get_next () from /usr/lib32/libudev.so.1 (gdb) bt #0 0x45b2e4a8 in udev_list_entry_get_next () from /usr/lib32/libudev.so.1 #1 0x45b33b8b in udev_monitor_filter_update () from /usr/lib32/libudev.so.1 #2 0xf788213e in udev_monitor_enable_receiving () from /home/abbradar/.steam/steam/SteamApps/common/GarrysMod/bin/libudev.so.0 #3 0xf795d7df in ?? () from /home/abbradar/.steam/steam/SteamApps/common/GarrysMod/bin/libSDL2-2.0.so.0 #4 0xf7948ae7 in ?? () from /home/abbradar/.steam/steam/SteamApps/common/GarrysMod/bin/libSDL2-2.0.so.0 #5 0xf78bf874 in SDL_InitSubSystem () from /home/abbradar/.steam/steam/SteamApps/common/GarrysMod/bin/libSDL2-2.0.so.0 #6 0xf789244f in ?? () from /home/abbradar/.local/share/Steam/SteamApps/common/GarrysMod/bin/inputsystem.so #7 0xf7890410 in ?? () from /home/abbradar/.local/share/Steam/SteamApps/common/GarrysMod/bin/inputsystem.so #8 0xf7f9bb36 in ?? () from bin/launcher.so #9 0xf7f9bc12 in ?? () from bin/launcher.so #10 0xf7f9be98 in ?? () from bin/launcher.so #11 0xf7f9beb0 in ?? () from bin/launcher.so #12 0xf7f83bbd in LauncherMain () from bin/launcher.so #13 0x080484d4 in main () (gdb) That's quite strange, no Mesa calls at all, yet new Mesa definitely breaks things...
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
