Debug - Revision history

Doom64hunter at 16:40, 6 September 2023

2023-09-06T16:40:12Z

← Older revision		Revision as of 09:40, 6 September 2023
Line 3:		Line 3:
	Prints <number> to the game log file and triggers a breakpoint if the binary has been compiled with `RELEASE=0`.		Prints <number> to the game log file and triggers a breakpoint if the binary has been compiled with `RELEASE=0`.

	Only useful for debugging if the process is attached to a debugger like gdb.		Only useful for debugging if the process is attached to a debugger like gdb. If not attached to a debugger, the game will simply close upon encountering the instruction.

	[[Category:Duke3D 1.3/1.5 commands]]		[[Category:Duke3D 1.3/1.5 commands]]

Doom64hunter at 16:28, 6 September 2023

2023-09-06T16:28:15Z

← Older revision		Revision as of 09:28, 6 September 2023
Line 3:		Line 3:
	Prints <number> to the game log file and triggers a breakpoint if the binary has been compiled with `RELEASE=0`.		Prints <number> to the game log file and triggers a breakpoint if the binary has been compiled with `RELEASE=0`.

	Only useful for debugging if the process is attached to debugger like gdb.		Only useful for debugging if the process is attached to a debugger like gdb.

	[[Category:Duke3D 1.3/1.5 commands]]		[[Category:Duke3D 1.3/1.5 commands]]

Doom64hunter at 16:28, 6 September 2023

2023-09-06T16:28:03Z

← Older revision		Revision as of 09:28, 6 September 2023
Line 1:		Line 1:
	'''debug''' <number>		'''debug''' <number>

	Prints <number> to the game log file and triggers a breakpoint.		Prints <number> to the game log file and triggers a breakpoint if the binary has been compiled with `RELEASE=0`.

	Only useful for debugging if the process is attached to debugger like gdb.		Only useful for debugging if the process is attached to debugger like gdb.

	[[Category:Duke3D 1.3/1.5 commands]]		[[Category:Duke3D 1.3/1.5 commands]]

Doom64hunter: Update description with actual use.

2023-09-06T15:34:06Z

Update description with actual use.

← Older revision		Revision as of 08:34, 6 September 2023
Line 1:		Line 1:
	'''debug''' <number>		'''debug''' <number>

	Prints <number> to the game log file. ~~This has little~~ to ~~no use. The [[echo]] command may be a better substitute~~.		Prints <number> to the game log file and triggers a breakpoint.

			Only useful for debugging if the process is attached to debugger like gdb.

	[[Category:Duke3D 1.3/1.5 commands]]		[[Category:Duke3D 1.3/1.5 commands]]

Hendricks266 at 07:27, 5 March 2012

2012-03-05T07:27:00Z

← Older revision		Revision as of 00:27, 5 March 2012
Line 1:		Line 1:
	'''debug''' <~~parameter~~>		'''debug''' <number>

	Prints <~~parameter~~> to the game log file.		Prints <number> to the game log file. This has little to no use. The [[echo]] command may be a better substitute.

	[[Category:Duke3D 1.3/1.5 commands]]		[[Category:Duke3D 1.3/1.5 commands]]

One at 19:02, 4 May 2009

2009-05-04T19:02:34Z

← Older revision		Revision as of 12:02, 4 May 2009
Line 1:		Line 1:
	debug <parameter>		'''debug''' <parameter>

	Prints <parameter> to the game log file.		Prints <parameter> to the game log file.

	[[Category:Duke3D 1.3/1.5 commands]]		[[Category:Duke3D 1.3/1.5 commands]]

TX: Text

2006-09-07T16:46:12Z

Text

← Older revision		Revision as of 09:46, 7 September 2006
Line 1:		Line 1:
	debug <parameter>		debug <parameter>

	~~This writes the values of~~ <parameter> to a log file ~~specified in the command line. Run it as "eduke32.exe > <filename>.log" to allow the values of any <parameter> using debug to be written to <filename>.log~~.		Prints <parameter> to the game log file.

	[[Category:Duke3D 1.3/1.5 commands]]		[[Category:Duke3D 1.3/1.5 commands]]

TX at 07:51, 24 September 2005

2005-09-24T07:51:40Z

← Older revision		Revision as of 00:51, 24 September 2005
Line 2:		Line 2:

	This writes the values of <parameter> to a log file specified in the command line. Run it as "eduke32.exe > <filename>.log" to allow the values of any <parameter> using debug to be written to <filename>.log.		This writes the values of <parameter> to a log file specified in the command line. Run it as "eduke32.exe > <filename>.log" to allow the values of any <parameter> using debug to be written to <filename>.log.

			[[Category:Duke3D 1.3/1.5 commands]]

BlasterDRP at 15:10, 24 December 2004

2004-12-24T15:10:30Z

New page

debug <parameter>

This writes the values of <parameter> to a log file specified in the command line. Run it as "eduke32.exe > <filename>.log" to allow the values of any <parameter> using debug to be written to <filename>.log.