![]() ![]() If you see the (gdb) prompt then FontForge is no longer executing. If you find that your interface is unresponsive, switch back to the terminal where you ran gdb and you might see something like "SIGSEGV" in the text followed by the (gdb) prompt. When you are running FontForge inside gdb however, a crashed FontForge will remain open along with its windows and user interface. Without gdb, when FontForge crashes it will disappear from your screen. One major difference that running FontForge inside gdb makes is how a crash is made apparent. Library based on sources from 14:57 GMT 3.įrom here you can use FontForge in the usual way, but with the advantage of being able to effectively capture and report any issues that FontForge may have. Using host libthread_db library "/lib64/libthread_db.so.1".Ĭopyright (c) 2000-2012 by George Williams.Įxecutable based on sources from 14:57 GMT 3-ML-TtfDb-D. Starting program: /usr/local/bin/fontforge Then once you issue the debugger the run command, FontForge will open on screen Reading symbols from /usr/local/bin/fontforge.done. This GDB was configured as "x86_64-redhat-linux-gnu".įor bug reporting instructions, please see: There is NO WARRANTY, to the extent permitted by law. This is free software: you are free to change and redistribute it. License GPLv3+: GNU GPL version 3 or later $ gdb fontforgeĬopyright (C) 2011 Free Software Foundation, Inc. You can either attach gdb to an already running FontForge, or start fontforge inside the gdb session itself as shown below. Using the GNU Debugger to report crashesĪ backtrace is generated using the GNU Project Debugger (gdb). Optionally, you might also like to mention what you were doing leading up to the crash. Because the backtrace will make reference to source files and line numbers, don't forget to also tell the developers which version of FontForge you are using. ![]() The backtrace is most useful if it also contains the line numbers of the functions. The backtrace includes a list of which program functions have called which other ones to get to where the program has stopped working. To help developers find out what is going wrong, they will want a backtrace from your session. You can then either patch your local FontForge, or just grab the sources from github as detailed in the Installing chapter to get an updated FontForge free of the defect you reported. This way, a software developer might be able to work out where the code is going wrong and apply a fix. If you find FontForge crashing whilst in use you might like to send information to the fontforge developer mailing list at. When things go wrong with FontForge itself
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |