Documentation/4.0/Developers/Tutorials/Debug Instructions - Revision history

UpdateBot: Prepend documentation/versioncheck template. See http://na-mic.org/Mantis/view.php?id=2887

2013-06-14T07:29:12Z

Prepend documentation/versioncheck template. See http://na-mic.org/Mantis/view.php?id=2887

Pieper: /* GDB debug by using exec-wrapper */

2012-03-05T13:37:20Z

GDB debug by using exec-wrapper

Finetjul: /* Linux */

2012-01-17T18:00:01Z

Linux

Finetjul: /* GDB debug with launch arguments */

2012-01-17T17:53:03Z

GDB debug with launch arguments

Finetjul: Move launcher information into the launcher page

2012-01-17T17:36:30Z

Move launcher information into the launcher page

Kikinis at 15:24, 21 November 2011

2011-11-21T15:24:46Z

JChris.FillionR at 03:23, 2 November 2011

2011-11-02T03:23:39Z

JChris.FillionR: moved Slicer4:Debug Instructions to Documentation/4.0/Developers/Tutorials/Debug Instructions

2011-11-02T03:20:47Z

moved Slicer4:Debug Instructions to Documentation/4.0/Developers/Tutorials/Debug Instructions

Pieper at 13:29, 12 October 2011

2011-10-12T13:29:21Z

Inorton: /* Linux */

2011-10-12T13:08:23Z

Linux

← Older revision		Revision as of 07:29, 14 June 2013
Line 1:		Line 1:
		+	<noinclude>{{documentation/versioncheck}}</noinclude>
	Back to [[Documentation/{{documentation/version}}/Developers\|Developers Information]]←		Back to [[Documentation/{{documentation/version}}/Developers\|Developers Information]]←

@@ Line 42: / Line 42: @@
 (gdb) run
 </pre>
 ===GDB debug in CodeLite IDE===

@@ Line 5: / Line 5: @@
 ==Linux==
 ===GDB debug with launch arguments===
 The Slicer app launcher provides options to start other programs with the Slicer environment settings.

@@ Line 8: / Line 8: @@
 The Slicer app launcher provides options to start other programs with the Slicer environment settings.
-*--launch: execute arbitrary program. For example, start gnome-terminal (then run GDB directly on SlicerQT-real)
+*<code>--launch <executable> [<parameters>]</code>: executes an arbitrary program. For example, <code>Slicer --launch /usr/bin/gnome-terminal</code> starts gnome-terminal (then run GDB directly on SlicerQT-real)
-*--gdb: run GDB. then exec SlicerQT-real from within the debugger environment.
+*<code>--gdb</code>: runs GDB then executes SlicerQT-real from within the debugger environment.
 ===GDB debug by attaching to running process===

@@ Line 2: / Line 2: @@
 ==Background==
-The executable Slicer application is: Slicer-build/Slicer (or Slicer.exe)
+The executable Slicer application ''Slicer-Superbuild/Slicer-build/Slicer'' (or Slicer.exe) is the [[Documentation/{{documentation/version}}/Developers/Launcher|launcher]] of the real application binary ''Slicer-Superbuild/Slicer-build/bin/SlicerQT-real''.
 ==Linux==

@@ Line 1: / Line 1: @@
-[[Documentation/{{documentation/version}}/Developers|Tutorials]]&larr;
+Back to [[Documentation/{{documentation/version}}/Developers|Developers Information]]&larr;
 ==Background==
 The executable Slicer application is: Slicer-build/Slicer (or Slicer.exe)

← Older revision		Revision as of 03:23, 2 November 2011
Line 1:		Line 1:
		+	[[Documentation/{{documentation/version}}/Developers\|Tutorials]]←
	==Background==		==Background==
	The executable Slicer application is: Slicer-build/Slicer (or Slicer.exe)		The executable Slicer application is: Slicer-build/Slicer (or Slicer.exe)

← Older revision	Revision as of 03:20, 2 November 2011
(No difference)

← Older revision		Revision as of 13:29, 12 October 2011
Line 40:		Line 40:
	===GDB debug in CodeLite IDE===		===GDB debug in CodeLite IDE===
	[[Slicer4:Linux_Debugging_CodeLite\|Linux debugging with CodeLite IDE]]		[[Slicer4:Linux_Debugging_CodeLite\|Linux debugging with CodeLite IDE]]
		+
		+	== Windows ==
		+
		+	For VisualStudio it's also possible to run the IDE with the correct environment to debug slicer.
		+
		+	The launcher gets configured with a special --VisualStudio option for this purpose.
		+
		+	Note that because CMake re-creates the solution file from within the build process, visual studio will sometimes need to stop and reload the project, requiring manual button pressing on your part. To avoid this, you can use a script to kick off the build and then re-start the IDE.
		+
		+	If you use cygwin, you can create simple shell scripts, for example in /usr/local/bin, which these several steps at once when run from the Slicer4-superbuild directory:
		+
		+	* ''s4build'' (slicer4 build)
		+	(cd Slicer-build; cmake.exe -VV --debug-output . && ./Slicer.exe --VisualStudio Slicer.sln /out buildlog.txt /build)
		+	(cd Slicer-build; ./Slicer.exe --VisualStudio Slicer.sln)
		+	* ''s4sbuild'' (slicer4 super build)
		+	(cmake.exe -VV --debug-output . && ./Slicer-build/Slicer.exe --VisualStudio Slicer.sln /out buildlog.txt /build)
		+	(cd Slicer-build; ./Slicer.exe --VisualStudio Slicer.sln)
		+
		+	The ''s4build'' command re-runs cmake and then runs the build of Slicer only. When this completes, it launches visual studio with slicer loaded for debugging.
		+
		+	''s4sbuild'' is similar, but it runs the superbuild process so that all the dependency libraries are updated. This takes longer, but is sometimes needed when there has been a change to CTK or other tools.
		+
		+	Note the buildlog.txt files for checking if anything went wrong.

← Older revision		Revision as of 13:08, 12 October 2011
Line 8:		Line 8:

	==Linux==		==Linux==
		+	===GDB debug with launch arguments===
		+	The Slicer app launcher provides options to start other programs with the Slicer environment settings.
		+
		+	*--launch: execute arbitrary program. For example, start gnome-terminal (then run GDB directly on SlicerQT-real)
		+	*--gdb: run GDB. then exec SlicerQT-real from within the debugger environment.

	===GDB debug by attaching to running process===		===GDB debug by attaching to running process===