Debugging Inkscape - Revision history

Adambelis: /* How to run Inkscape in debug mode */

Adambelis — Wed, 18 Nov 2020 13:15:37 GMT

How to run Inkscape in debug mode

← Older revision		Revision as of 13:15, 18 November 2020
Line 30:		Line 30:
	# Open command prompt (cmd)		# Open command prompt (cmd)
	# Type <code>set GTK_DEBUG=interactive</code> and hit enter		# Type <code>set GTK_DEBUG=interactive</code> and hit enter
	# Then <code>C:\Program Files\Inkscape\bin\inkscape.exe</code> or however you launch Inkscape from the same command prompt		# Then <code>C:\Program Files\Inkscape\bin\inkscape.exe</code> or however you launch Inkscape from the same command prompt. Path cannot have any spaces.
	# After that Inkscape will start ~~wit~~ gtk inspector running		# After that Inkscape will start with gtk inspector running

	First, have a look at the [[Using Visual Studio]] page for how to use that program on Windows to debug Inkscape.		First, have a look at the [[Using Visual Studio]] page for how to use that program on Windows to debug Inkscape.

Adambelis: /* How to run in debug mode */

Adambelis — Wed, 18 Nov 2020 09:25:26 GMT

How to run in debug mode

← Older revision		Revision as of 09:25, 18 November 2020
Line 27:		Line 27:

	== Debugging Tips for Windows ==		== Debugging Tips for Windows ==
	=== How to run in debug mode ===		=== How to run Inkscape in debug mode ===
	# Open command prompt (cmd)		# Open command prompt (cmd)
	# Type <code>set GTK_DEBUG=interactive</code> and hit enter		# Type <code>set GTK_DEBUG=interactive</code> and hit enter

Adambelis: /* Debugging Tips for Windows */

Adambelis — Wed, 18 Nov 2020 08:35:01 GMT

Debugging Tips for Windows

← Older revision		Revision as of 08:35, 18 November 2020
Line 31:		Line 31:
	# Type <code>set GTK_DEBUG=interactive</code> and hit enter		# Type <code>set GTK_DEBUG=interactive</code> and hit enter
	# Then <code>C:\Program Files\Inkscape\bin\inkscape.exe</code> or however you launch Inkscape from the same command prompt		# Then <code>C:\Program Files\Inkscape\bin\inkscape.exe</code> or however you launch Inkscape from the same command prompt
	# After that ~~inkscape~~ will start wit gtk inspector		# After that Inkscape will start wit gtk inspector running

	First, have a look at the [[Using Visual Studio]] page for how to use that program on Windows to debug Inkscape.		First, have a look at the [[Using Visual Studio]] page for how to use that program on Windows to debug Inkscape.

Adambelis: /* How to run in debug mode */

Adambelis — Wed, 18 Nov 2020 08:34:41 GMT

How to run in debug mode

← Older revision		Revision as of 08:34, 18 November 2020
Line 28:		Line 28:
	== Debugging Tips for Windows ==		== Debugging Tips for Windows ==
	=== How to run in debug mode ===		=== How to run in debug mode ===
	# ~~1.open~~ command prompt (cmd)		# Open command prompt (cmd)
	# ~~2.type~~ <code>set GTK_DEBUG=interactive</code> and hit enter		# Type <code>set GTK_DEBUG=interactive</code> and hit enter
	# ~~3.then "~~C:\Program Files\Inkscape\bin\inkscape.exe" or however you launch Inkscape from the same command prompt		# Then <code>C:\Program Files\Inkscape\bin\inkscape.exe</code> or however you launch Inkscape from the same command prompt
			# After that inkscape will start wit gtk inspector

	First, have a look at the [[Using Visual Studio]] page for how to use that program on Windows to debug Inkscape.		First, have a look at the [[Using Visual Studio]] page for how to use that program on Windows to debug Inkscape.

Adambelis: /* How to run in debug mode */

Adambelis — Wed, 18 Nov 2020 08:33:21 GMT

How to run in debug mode

← Older revision		Revision as of 08:33, 18 November 2020
Line 28:		Line 28:
	== Debugging Tips for Windows ==		== Debugging Tips for Windows ==
	=== How to run in debug mode ===		=== How to run in debug mode ===
	1.open command prompt (cmd)		# 1.open command prompt (cmd)
	2.type <code>set GTK_DEBUG=interactive</code> and hit enter		# 2.type <code>set GTK_DEBUG=interactive</code> and hit enter
	3.then "C:\Program Files\Inkscape\bin\inkscape.exe" or however you launch Inkscape from the same command prompt		# 3.then "C:\Program Files\Inkscape\bin\inkscape.exe" or however you launch Inkscape from the same command prompt

	First, have a look at the [[Using Visual Studio]] page for how to use that program on Windows to debug Inkscape.		First, have a look at the [[Using Visual Studio]] page for how to use that program on Windows to debug Inkscape.

Adambelis: /* Debugging Tips for Windows */

Adambelis — Wed, 18 Nov 2020 08:30:58 GMT

Debugging Tips for Windows

← Older revision		Revision as of 08:30, 18 November 2020
Line 27:		Line 27:

	== Debugging Tips for Windows ==		== Debugging Tips for Windows ==
			=== How to run in debug mode ===
			1.open command prompt (cmd)
			2.type <code>set GTK_DEBUG=interactive</code> and hit enter
			3.then "C:\Program Files\Inkscape\bin\inkscape.exe" or however you launch Inkscape from the same command prompt

	First, have a look at the [[Using Visual Studio]] page for how to use that program on Windows to debug Inkscape.		First, have a look at the [[Using Visual Studio]] page for how to use that program on Windows to debug Inkscape.

Speleo3: G_DEBUG=fatal-warnings

Speleo3 — Mon, 25 Nov 2019 07:47:33 GMT

G_DEBUG=fatal-warnings

← Older revision		Revision as of 07:47, 25 November 2019
Line 1:		Line 1:
	* 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")		* If you're hunting down a GTK warning, run <code>G_DEBUG=fatal-warnings gdb inkscape</code> so you can capture a backtrace. ("run", "bt")

	* If you're hunting down a g_assert, you can set a breakpoint in gdb for "g_assertion_message_expr" (or "g_assertion_message" maybe) to stop execution and make a backtrace.		* If you're hunting down a g_assert, you can set a breakpoint in gdb for "g_assertion_message_expr" (or "g_assertion_message" maybe) to stop execution and make a backtrace.

BitBarrel: /* Debugging Tips for Windows */ Changed Using Eclipse link to Using Visual Studio

BitBarrel — Thu, 05 Mar 2015 09:11:52 GMT

Debugging Tips for Windows: Changed Using Eclipse link to Using Visual Studio

← Older revision		Revision as of 09:11, 5 March 2015
Line 28:		Line 28:
	== Debugging Tips for Windows ==		== Debugging Tips for Windows ==

	First, have a look at the [[Using ~~Eclipse~~]] page for how to use that program on Windows to debug Inkscape.		First, have a look at the [[Using Visual Studio]] 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()..		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()..

Jan m: /* Problems running GDB */

Jan m — Sat, 25 Jul 2009 18:15:13 GMT

Problems running GDB

← Older revision		Revision as of 18:15, 25 July 2009
Line 129:		Line 129:

	This has stumped me once before, but this time I checked out the help menus, and found under "help running" that I could simply type "continue". I figured that xslDebugStatus was nothing to do with the Inkscape program itself, but more to do with gdb, and after typing "continue" it seems to run Inkscape under gdb as normal, allowing backtraces.		This has stumped me once before, but this time I checked out the help menus, and found under "help running" that I could simply type "continue". I figured that xslDebugStatus was nothing to do with the Inkscape program itself, but more to do with gdb, and after typing "continue" it seems to run Inkscape under gdb as normal, allowing backtraces.

			===guard32.dll error===
			If you try to run gdb but it halts, complaining about guard32.dll, your Comodo Firewall installation is blocking gdb. Easiest way around this is to '''disable the Defense+ module completely''' -- open up Comodo Firewall, click on Defense+, Defense+ settings, set Security Level to "Disabled", and check "Deactivate the Defense+ permanently". Reboot.

	== Debugging Tips for Linux ==		== Debugging Tips for Linux ==

Tweenk: moved DebuggingTips to Debugging Inkscape: kill wikiwords

Tweenk — Fri, 19 Jun 2009 15:30:03 GMT

moved DebuggingTips to Debugging Inkscape: kill wikiwords

← Older revision	Revision as of 15:30, 19 June 2009
(No difference)