Ok, I installed libgdk-3-0-dbg and managed to get here: (gdb) break gdk_x_error Function "gdk_x_error" not defined. Make breakpoint pending on future shared library load? (y or [n]) y Breakpoint 1 (gdk_x_error) pending. (gdb) run far.pdf Starting program: /usr/bin/evince far.pdf [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x7fffee0aa700 (LWP 8026)] [New Thread 0x7fffed8a9700 (LWP 8027)] [New Thread 0x7fffed062700 (LWP 8031)] [New Thread 0x7fffdffff700 (LWP 8032)] [New Thread 0x7fffdf77e700 (LWP 8033)] [New Thread 0x7fffdcee7700 (LWP 8034)] [New Thread 0x7fffd7fff700 (LWP 8035)] [New Thread 0x7fffd77fe700 (LWP 8036)] [Thread 0x7fffed8a9700 (LWP 8027) exited] [Thread 0x7fffd77fe700 (LWP 8036) exited] [Thread 0x7fffd7fff700 (LWP 8035) exited]
Breakpoint 1, gdk_x_error (xdisplay=0x6a1340, error=0x7fffffffdb80) at /tmp/buildd/gtk+3.0-3.14.5/./gdk/x11/gdkmain-x11.c:268 268 /tmp/buildd/gtk+3.0-3.14.5/./gdk/x11/gdkmain-x11.c: No such file or directory. On Wed, May 31, 2017 at 3:53 PM, Sotiris Kouvopoulos <sotk...@gmail.com> wrote: > I am using xfce. > > Excuse me if I did something wrong, this is the first time I am trying to > do something like this. > First I installed evince-dbg package (followed instructions at > https://wiki.debian.org/HowToGetABacktrace) > I used the following to start gdb: > $ GDK_SYNCHRONIZE=1 gdb evince > > output: > GNU gdb (Debian 7.7.1+dfsg-5) 7.7.1 > Copyright (C) 2014 Free Software Foundation, Inc. > License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl. > html> > This is free software: you are free to change and redistribute it. > There is NO WARRANTY, to the extent permitted by law. Type "show copying" > and "show warranty" for details. > This GDB was configured as "x86_64-linux-gnu". > Type "show configuration" for configuration details. > For bug reporting instructions, please see: > <http://www.gnu.org/software/gdb/bugs/>. > Find the GDB manual and other documentation resources online at: > <http://www.gnu.org/software/gdb/documentation/>. > For help, type "help". > Type "apropos word" to search for commands related to "word"... > Reading symbols from evince...Reading symbols from /usr/lib/debug//usr/bin/ > evince...done. > done. > > Then I did: > (gdb) run far.pdf > > output: > Starting program: /usr/bin/evince far.pdf > [Thread debugging using libthread_db enabled] > Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". > [New Thread 0x7fffee0aa700 (LWP 7681)] > [New Thread 0x7fffed8a9700 (LWP 7682)] > [New Thread 0x7fffed062700 (LWP 7686)] > [New Thread 0x7fffdffff700 (LWP 7687)] > [New Thread 0x7fffdf77e700 (LWP 7688)] > [New Thread 0x7fffdcee7700 (LWP 7689)] > [Thread 0x7fffed8a9700 (LWP 7682) exited] > > (evince:7677): Gdk-ERROR **: The program 'evince' received an X Window > System error. > This probably reflects a bug in the program. > The error was 'BadWindow (invalid Window parameter)'. > (Details: serial 5467 error_code 3 request_code 141 (Composite) > minor_code 8) > (Note to programmers: normally, X errors are reported asynchronously; > that is, you will receive the error a while after causing it. > To debug your program, run it with the GDK_SYNCHRONIZE environment > variable to change this behavior. You can then get a meaningful > backtrace from your debugger if you break on the gdk_x_error() > function.) > > Program received signal SIGTRAP, Trace/breakpoint trap. > 0x00007ffff4dc9d30 in g_logv () from /lib/x86_64-linux-gnu/libglib- > 2.0.so.0 > > At this point the system runs but UI is not responsive so i had to kill > gdb from a terminal. > I hope there is some information in all the above. > > > > > On Fri, May 26, 2017 at 8:30 PM, Jason Crain <ja...@inspiresomeone.us> > wrote: > >> Control: tags -1 + moreinfo >> >> On Fri, May 26, 2017 at 06:25:52PM +0300, Sotiris Kouvopoulos wrote: >> > When I select some text, for example a simple word and try to drag the >> > selection (hold left mouse button and move mouse) the application >> crashes >> > immediately. >> > >> > This is the output when evince is started from terminal: >> > (evince:7977): Gdk-ERROR **: The program 'evince' received an X Window >> > System error. >> > This probably reflects a bug in the program. >> > The error was 'BadWindow (invalid Window parameter)'. >> > (Details: serial 3201 error_code 3 request_code 141 (Composite) >> > minor_code 8) >> > (Note to programmers: normally, X errors are reported asynchronously; >> > that is, you will receive the error a while after causing it. >> > To debug your program, run it with the GDK_SYNCHRONIZE environment >> > variable to change this behavior. You can then get a meaningful >> > backtrace from your debugger if you break on the gdk_x_error() >> function.) >> > Trace/breakpoint trap >> >> I can't reproduce this. What desktop environment are you using? If you >> are able, a backtrace with debug symbols and GDK_SYNCHRONIZE=1 as in >> that error message would be helpful. >> > > > > -- > Sotiris Kouvopoulos--- > Architect------------- > Ydras 6A, Athens------ > cadu.gr <http://www.cadu.gr>--------------- > tel: +302108839103 <+30%2021%200883%209103>---- > mob: +306976860989 <+30%20697%20686%200989>---- > -- Sotiris Kouvopoulos--- Architect------------- Ydras 6A, Athens------ cadu.gr <http://www.cadu.gr>--------------- tel: +302108839103---- mob: +306976860989----