I was trying to see what happens when I open a test case pdf using evince with the debug options. Thanks for the suggestions :)
On Mon, Sep 15, 2014 at 7:14 PM, Giselle Reis <[email protected]> wrote: > Hi Eejya, > > what are you trying to debug exactly? > I know many people use nemiver, although I was not able to use it > myself... You can give it a try. > I tried gdb at some point and managed to run it with the following: > > libtool --mode=execute gdb --args ./shell/evince > > Other than that, I was mostly going for memory checking. The EV_PROFILER > flag (or something like this) helped a lot, together with valgrind. > > Cheers, > Giselle > > > > > On Mon, Sep 15, 2014 at 3:32 PM, Eejya Singh <[email protected]> > wrote: > >> Hi, >> I tried enabling the debug option in evince by using the following >> command: >> ./configure --enable-debug in the ~/jhbuild/checkout/evince folder. >> I then set the EV_DEBUG_JOBS flag to 1 while running evince something >> like: >> EV_DEBUG_JOBS=1 evince [path to the pdf/pdfname.pdf] >> However on closing the window nothing is shown on the terminal. >> What could be the problem? >> Appreciate the help :) >> >> -- >> Eejya Singh, >> 2nd year undergraduate, >> Computer Science, >> BITS Pilani Goa Campus >> >> _______________________________________________ >> gnome-love mailing list >> [email protected] >> https://mail.gnome.org/mailman/listinfo/gnome-love >> >> > -- Eejya Singh, 2nd year undergraduate, Computer Science, BITS Pilani Goa Campus
_______________________________________________ gnome-love mailing list [email protected] https://mail.gnome.org/mailman/listinfo/gnome-love
