Debugging Metamod:Source on Linux - Revision history

BAILOPAN: Debugging SourceMM on Linux moved to Debugging Metamod:Source on Linux

2007-10-06T04:54:33Z

Debugging SourceMM on Linux moved to Debugging Metamod:Source on Linux

BAILOPAN at 04:54, 6 October 2007

2007-10-06T04:54:26Z

BAILOPAN: /* Notes */

2006-01-21T20:35:23Z

‎Notes

BAILOPAN: /* Notes */

2006-01-21T20:34:38Z

‎Notes

BAILOPAN at 20:32, 21 January 2006

2006-01-21T20:32:55Z

New page

==Introduction==
To debug your [[SourceMM]] plugin on Linux, you should have gdb (Gnu DeBugger) and g++ 3.4.

==Steps==
#Compile your plugin with -O0 -g -ggdb3. This will ensure your plugin has debug symbols compiled in. You should not be using high optimization flags or stripping symbols (-s).
#In your shell (for bash), type: <pre>export LD_LIBRARY_PATH=".:bin:$LD_LIBRARY_PATH"</pre>
#In your directory that contains srcds_run, type: <pre>gdb srcds_i686</pre>
#*Note: this assumes that your processor is i686. There is also srcds_amd and srcds_i486 -- run the one that is best described by your CPU.
#In GDB, type your startup command line prepended by "run", like so: <pre>run -game cstrike +map de_dust +ip 127.0.0.1 +maxplayers 16</pre>
#Once your server crashes, you can use <tt>bt</tt> to see a backtrace. To jump to a particular frame of the backtrace, you can use <tt>frame <n></tt>.

==Notes==
*To break into the debugger, use CTRL+C.
*To continue after breaking, use <tt>cont</tt>.
*To print an expression, use <tt>print <expr></tt>. You can print address contents, C expressions, previous expression results, and variable contents if the names are available in the frame.
*For disassembling..
**Use <tt>set disas intel</tt> for proper Intel assembly output.
**Use <tt>display/i $pc</tt> to see the current eip and its disassembly.
**Use <tt>disas <addr|expr></tt> to disassemble an address or expression.
**Use <tt>info all</tt> to see the CPU register layout.
*Use <tt>step</tt> and <tt>next</tt> for stepping into and over lines of code (also <tt>s</tt> and <tt>n</tt>).
*Use <tt>stepi</tt> and <tt>nexti</tt> for stepping into and over individual instructions (also <tt>si</tt> and <tt>ni</tt>.

[[Category:Documentation (SourceMM)]]

@@ Line 1: / Line 1: @@
 ==Introduction==
-To debug your [[SourceMM]] plugin on Linux, you should have gdb (Gnu DeBugger) and g++ 3.4.
+To debug your [[Metamod:Source]] plugin on Linux, you should have gdb (Gnu DeBugger) and g++ 3.4.
 ==Steps==
@@ Line 23: / Line 23: @@
 *Use <tt>stepi</tt> and <tt>nexti</tt> for stepping into and over individual instructions (also <tt>si</tt> and <tt>ni</tt>).
-[[Category:Documentation (SourceMM)]]
+[[Category:Metamod:Source Development]]

← Older revision	Revision as of 04:54, 6 October 2007
(No difference)

@@ Line 21: / Line 21: @@
 **Use <tt>info all</tt> to see the CPU register layout.
 *Use <tt>step</tt> and <tt>next</tt> for stepping into and over lines of code (also <tt>s</tt> and <tt>n</tt>).
-*Use <tt>stepi</tt> and <tt>nexti</tt> for stepping into and over individual instructions (also <tt>si</tt> and <tt>ni</tt>.
+*Use <tt>stepi</tt> and <tt>nexti</tt> for stepping into and over individual instructions (also <tt>si</tt> and <tt>ni</tt>).
 [[Category:Documentation (SourceMM)]]

@@ Line 17: / Line 17: @@
 **Use <tt>set disas intel</tt> for proper Intel assembly output.
 **Use <tt>display/i $pc</tt> to see the current eip and its disassembly.
 **Use <tt>disas &lt;addr|expr></tt> to disassemble an address or expression.
 **Use <tt>info all</tt> to see the CPU register layout.