-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Ian Romanick: > On 01/16/2014 10:42 PM, scarp wrote: >> Hi, > >> I originally posted this to dri-users and got no response. I >> thought about it further and decided it's really a bug and >> deserves to be posted to dri-devel, after all it is a crash and >> crashes are supposed to be handled. > > These days dri-* is generally for kernel related discussions. > mesa-* is the right place. I'm moving the discussion to mesa-dev. >
Ah okay, I wasn't aware of this. >> Any custom configurations provided by Whonix can be found in: > >> Gateway VM that has Tor process: >> https://github.com/adrelanos/Whonix/tree/master/whonix_gateway > >> Shared, files that are used in both virtual machines >> https://github.com/adrelanos/Whonix/tree/master/whonix_shared > >> Files only used in the Workstation VM >> https://github.com/adrelanos/Whonix/tree/master/whonix_workstation > >> > >> In case this is something like a grub config option or something >> like that is why I posted these. > > >> -------- Original Message -------- Subject: munmap_chunk(): >> invalid pointer in libgl1-mesa-dri_9.2.1-1 Date: Thu, 26 Dec 2013 >> 07:13:45 +0000 From: scarp <sc...@riseup.net> To: >> dri-us...@lists.freedesktop.org > >> Hi, > >> I've been testing the privacy orientated virtual machine >> distribution Whonix http://whonix.org. It's a Debian blend >> specifically designed to be an anonymous operating system. In >> this case I am using the latest VirtualBox (4.3.6) - without >> guest utilities. > >> Recently I started having some problems with xvideo, in things >> like mplayer and vlc, and also glxinfo from mesa-utils. Where >> they would simply crash with an error and a backtrace. Exactly >> this one: (full crash attached) > >> *** Error in `glxinfo': munmap_chunk(): invalid pointer: >> 0x000000000138d8a0 *** ======= Backtrace: ========= >> /lib/x86_64-linux-gnu/libc.so.6(+0x7aa16)[0x7f88a36f2a16] >> /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so(+0x248688)[0x7f88a04e6688] > >> > > /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so(+0x3263a3)[0x7f88a05c43a3] >> > /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so(+0x14f412)[0x7f88a03ed412] > > > /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so(dri_destroy_context+0x38)[0x7f88a0597a58] >> > /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so(+0x450c3)[0x7f88a02e30c3] > > > /usr/lib/x86_64-linux-gnu/libGL.so.1(+0x3b34f)[0x7f88a42aa34f] >> /usr/lib/x86_64-linux-gnu/libGL.so.1(+0x1c281)[0x7f88a428b281] >> /usr/lib/x86_64-linux-gnu/libGL.so.1(+0x1c305)[0x7f88a428b305] >> /usr/lib/x86_64-linux-gnu/libX11.so.6(XCloseDisplay+0xa2)[0x7f88a3c55c02] > >> > > glxinfo[0x401c14] >> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7f88a3699995] > >> > > glxinfo[0x401ee6] > > If this distro has "debug" packages, you should install those for > libgl1-mesa-dri. That way the backtrace can have source file > names and line numbers. You might also try running with valgrind. > I should have made this clear. Whonix doesn't use any of it's own binary packages, it's all debian testing 100%. My only guess is some configuration Whonix uses is triggering this regression, because the previous version of libgl1-mesa-dri worked perfectly. The few configuration changes such as /etc/default/grub* can be found in the github repositories however. I installed libgl1-mesa-dri-dbg gdb valgrind mesa-utils however I'm still seeing some: <optimized out> do I need something else? This time I ran glxinfo in gdb and ordered a backtrace: as in $ gdb glxinfo (gdb) run (gdb) bt Program received signal SIGABRT, Aborted. 0x00007ffff6ac11d5 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 56 ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory. (gdb) bt #0 0x00007ffff6ac11d5 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #1 0x00007ffff6ac4388 in __GI_abort () at abort.c:90 #2 0x00007ffff6afc7bb in __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7ffff6bf9368 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:199 #3 0x00007ffff6b06a16 in malloc_printerr (action=3, str=0x7ffff6bf9450 "munmap_chunk(): invalid pointer", ptr=<optimized out>) at malloc.c:4923 #4 0x00007ffff38f9688 in util_blitter_destroy (blitter=0x677530) at ../../../../../src/gallium/auxiliary/util/u_blitter.c:341 #5 0x00007ffff39d73a3 in llvmpipe_destroy (pipe=0x633ae0) at ../../../../../../src/gallium/drivers/llvmpipe/lp_context.c:62 #6 0x00007ffff3800412 in st_destroy_context (st=0x0) at ../../../../src/mesa/state_tracker/st_context.c:319 #7 0x00007ffff39aaa58 in dri_destroy_context (cPriv=<optimized out>) at ../../../../../../../src/gallium/state_trackers/dri/sw/dri_context.c:203 #8 0x00007ffff36f60c3 in driDestroyContext (pcp=0x632b50) at ../../../../../../src/mesa/drivers/dri/common/drisw_util.c:229 #9 0x00007ffff76be34f in ?? () from /usr/lib/x86_64-linux-gnu/libGL.so.1 #10 0x00007ffff769f281 in ?? () from /usr/lib/x86_64-linux-gnu/libGL.so.1 #11 0x00007ffff769f305 in ?? () from /usr/lib/x86_64-linux-gnu/libGL.so.1 #12 0x00007ffff7069c02 in XCloseDisplay () from /usr/lib/x86_64-linux-gnu/libX11.so.6 #13 0x0000000000401c14 in ?? () #14 0x00007ffff6aad995 in __libc_start_main (main=0x401540, argc=1, ubp_av=0x7fffffffe228, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffffffe218) at libc-start.c:276 #15 0x0000000000401ee6 in ?? () >> I discovered the problem was directly related to >> libgl1-mesa-dri. Rolling back to the previous version of the >> package made the problem disappear. > >> libgl1-mesa-dri_9.1.7-1 works >> http://snapshot.debian.org/package/mesa/9.1.7-1/#libgl1-mesa-dri_9.1.7-1 > >> libgl1-mesa-dri_9.2.1-1 doesn't >> http://snapshot.debian.org/package/mesa/9.2-1/#libgl1-mesa-dri_9.2-1 > >> I'm wondering what could have changed in between these two >> versions? > >> I installed the whole "xorg" metapackage from Debian and it >> didn't seem to help. I thought maybe some functionality of >> libgl1-mesa-dri might have been modularized into another >> package. Rolling that package back seemed to fix it. > >> Whonix by default uses KDE, however I was able to reproduce the >> crash when using TWM as well. > >> The interesting thing is I couldn't reproduce it with a stock >> standard desktop install from debian-testing-amd64-kde-CD-1.iso >> I did a comparison of the packages installed ie dpkg -l in both >> Whonix and debian-testing-amd64-kde-CD-1.iso and didn't find >> that anything was missing. > >> It has been reported by one other user >> https://www.whonix.org/wiki/Special:AWCforum/st/id282/vlc_video_crash.html > >> > > and while a work around for VLC was found it doesn't really solve > this >> issue. > >> If anyone doesn't know what could be causing this perhaps you >> can give me some tips on how to find out what is. > - -- scarp | A4F7 25DB 2529 CB1A 605B 3CB4 5DA0 4859 0FD4 B313 -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJS2mVmAAoJEF2gSFkP1LMTA1cP/12Y1AGE1aUZT5l8xTH1r59a LQdHYfB2rdJ6ieTU6kSG6OY+6Cc6pjjezrpup48U1iZOEncRvoJr5/eF/qlqaQX1 A/Rij9PnP/ttrLiBAqddAef1TLBKmzQff1Affvf90G570GUC36xq/x4zsqvOVKwq Fa8gdJFmeC2g4Ad16FrlMAtu7Qe+XRgv5QoO10ysziR/uzIJeWavQKalWHZV6bVG D2USaAIigfvOZfpU4ylAuitvzKbQoIx+2gcr5fxlh4zS8m+PG7R5jZgWNMx2XPBb 1C3mzkeRRtr/jHgjlbaGmLQ74Pg+P2fRl4IzsGx/l19zPhxs6JthwKAnY0akSU2S BlIgJsswKWN63efAYAlunEiF5NkPEJcGpVsFZVJ4DLrqV3SzGKVbvmnA6exirjBD 9zbCSYYeFluzh7M+lkjBooTVSSnlZZN1Onbc9/XToKep1sCmFsH4MdcIALLTTH1/ 19psJzxIiXe/V+cnRy+/OSNpBsGmWNOsl3NKe3Pjs0LQcJrEDY5pYruZpY5+QW7z j16lI/QtvB3YQ/DYhPmifcthdCvMYJ6FLZ+9stjVLKKsHeQ6uNXXrQ60WoCRVUn1 LgjqyDkZnaZLK9BHJD+N+g+/C2e/Y1PzmWMdWTA0N6biuDHexmkIx7N2EyYCknrj U94J9Hh2nHZ9mNcJqL8k =hob7 -----END PGP SIGNATURE----- _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
