Difference between revisions of "Debugging Inkscape"
Jump to navigation
Jump to search
(Categorization) |
(Tips for debugging on Windows) |
||
| Line 3: | Line 3: | ||
* Bug list | * Bug list | ||
- w32 version asks for (that crappy) Verdana typeface (which is not the most usual w32 typeface, also some users have deleted it to save disk space) | - w32 version asks for (that crappy) Verdana typeface (which is not the most usual w32 typeface, also some users have deleted it to save disk space) | ||
== Debugging Tips for Windows == | |||
First, have a look at the [[Using Eclipse]] page for how to use that program on Windows to debug Inkscape. | |||
Second, make use of the '''View > Messages...''' dialog from within the program. Capturing the log here will show you messages printed with g_message(), g_warning(), and g_error().. | |||
Finally, look into [http://wiki.inkscape.org/wiki/index.php/FAQ#I.27m_on_Windows.2C_and_command_line_parameters_don.27t_seem_to_work.21 how to compile Eclipse as a command line app] so you can capture debug messages at the prompt, more like you would do in Linux. | |||
[[Category:Developer Documentation]] | [[Category:Developer Documentation]] | ||
Revision as of 19:29, 20 June 2007
- If you're hunting down a GTK warning, you can set a breakpoint in gdb for "g_logv" so you can capture a backtrace. ("br g_logv", "run", "bt")
- Bug list
- w32 version asks for (that crappy) Verdana typeface (which is not the most usual w32 typeface, also some users have deleted it to save disk space)
Debugging Tips for Windows
First, have a look at the Using Eclipse page for how to use that program on Windows to debug Inkscape.
Second, make use of the View > Messages... dialog from within the program. Capturing the log here will show you messages printed with g_message(), g_warning(), and g_error()..
Finally, look into how to compile Eclipse as a command line app so you can capture debug messages at the prompt, more like you would do in Linux.