← Older revision

Revision as of 09:33, 6 September 2013

Line 22:

===Getting a backtrace (aka stack trace)===

===Getting a backtrace (aka stack trace)===

Once you have got an application running under GDB, you can easily get a backtrace, which will display the sequence of functions that were called to arrive at the point where the debugger is currently stopped.

Once you have got an application running under GDB, you can easily get a backtrace, which will display the sequence of functions that were called to arrive at the point where the debugger is currently stopped.

+

[http://vamostech.com/gps-tracking GPS Tracking VT 100], [http://www.pedatimotor.com Aksesoris Sparepart Motor Matic], [http://www.detikauto.com Aksesoris Mobil], [http://www.detikauto.com Variasi Mobil], [http://www.yourbutik.com Parfum], [http://mariposa-store.com/ Jual Sepatu Online]

  (gdb) '''bt'''

  (gdb) '''bt'''

Line 47:

Line 48:

==Valgrind / Memory Leaks==

==Valgrind / Memory Leaks==

−

To check for memory leaks, you can try [http://valgrind.org/ Valgrind]. Note, however, that Net-SNMP relies on the operating system to cleanup memory when an application exits, so there will be lots of un-released memory when the application exits.  Please don't report this as a bug. We are only interested in memory leaks that grow over time.

+

To check for memory leaks, you can try. Note, however, that Net-SNMP relies on the operating system to cleanup memory when an application exits, so there will be lots of un-released memory when the application exits.  Please don't report this as a bug. We are only interested in memory leaks that grow over time.

If you don't want to read the Valgrind docs, here is a quick example:

If you don't want to read the Valgrind docs, here is a quick example:

Line 56:

Line 57:

==Dmalloc==

==Dmalloc==

−

Detecting memory errors in Net-SNMP is not only possible with Valgrind but also with [http://dmalloc.com/ Dmalloc]. While Valgrind is more powerful than Dmalloc, Dmalloc is supported on more platforms than Valgrind (e.g. Solaris and Cygwin). Proceed as follows to analyze Net-SNMP with Dmalloc:

+

Detecting memory errors in Net-SNMP is not only possible with Valgrind but also with. While Valgrind is more powerful than Dmalloc, Dmalloc is supported on more platforms than Valgrind (e.g. Solaris and Cygwin). Proceed as follows to analyze Net-SNMP with Dmalloc:

# Install dmalloc.

# Install dmalloc.

# Modify <dmalloc.h> and insert #undef strndup just before the declaration of strndup().

# Modify <dmalloc.h> and insert #undef strndup just before the declaration of strndup().

# Configure Net-SNMP with the option --with-dmalloc=<dmalloc prefix>.

# Configure Net-SNMP with the option --with-dmalloc=<dmalloc prefix>.

# Build Net-SNMP.

# Build Net-SNMP.

−

# Make sure that the dmalloc function has been defined in your shell. See also the [http://dmalloc.com/docs/latest/online/dmalloc_4.html dmalloc manual] for the details.

+

# Make sure that the dmalloc function has been defined in your shell. See also the for the details.

# Set dmalloc options, e.g. <pre>dmalloc high -p print-messages</pre>

# Set dmalloc options, e.g. <pre>dmalloc high -p print-messages</pre>

# Start Net-SNMP, e.g. as follows: <pre>agent/snmpd -f -Lo -Mmibs</pre>

# Start Net-SNMP, e.g. as follows: <pre>agent/snmpd -f -Lo -Mmibs</pre>

Line 94:

Line 95:

==References==

==References==

−

* [http://fedoraproject.org/wiki/StackTraces Stack traces for Fedora RPM packages]

−

* [http://linux.bytesex.org/gdb.html gdb mini intro]

Debugger - Revision history

Wes: Reverted edits by Domtheo (talk) to last revision by Tanders

Domtheo at 09:33, 6 September 2013