aboutsummaryrefslogtreecommitdiffstats
path: root/docbook
diff options
context:
space:
mode:
authorGuy Harris <guy@alum.mit.edu>2018-04-24 21:39:30 -0700
committerGuy Harris <guy@alum.mit.edu>2018-04-25 04:40:04 +0000
commit067a67bd270a9db08c2bf5f695e3c5aaa80fc176 (patch)
tree8adaec3c788d2b4ad5431d8f86e92bcc1d867dc0 /docbook
parent9e8f8921a3fb61f0170776505ed80f3989019cf3 (diff)
Remove some references to autotools from developer documentation.
Change-Id: I4c95e56e067eed98d269812225256462dfa46273 Reviewed-on: https://code.wireshark.org/review/27140 Reviewed-by: Guy Harris <guy@alum.mit.edu>
Diffstat (limited to 'docbook')
-rw-r--r--docbook/wsdg_src/WSDG_chapter_sources.asciidoc17
1 files changed, 4 insertions, 13 deletions
diff --git a/docbook/wsdg_src/WSDG_chapter_sources.asciidoc b/docbook/wsdg_src/WSDG_chapter_sources.asciidoc
index bc8d9cbb46..9a4e7fe278 100644
--- a/docbook/wsdg_src/WSDG_chapter_sources.asciidoc
+++ b/docbook/wsdg_src/WSDG_chapter_sources.asciidoc
@@ -466,25 +466,16 @@ launching the Wireshark.exe executable.
==== Unix/Linux
-When you want to investigate a problem with Wireshark you want to load
-the program into your debugger. But loading wireshark into debugger fails
-because of the libtool build environment. You'll have to wrap loading
-wireshark into a libtool command:
-
-[source,sh]
-----
-$ libtool --mode=execute gdb wireshark
-----
-
-If you prefer a graphic debugger you can use the Data Display Debugger
-(ddd) instead of GNU debugger (gdb).
+You can debug using command-line debuggers such as gdb, dbx, or lldb.
+If you prefer a graphic debugger, you can use the Data Display Debugger
+(ddd).
Additional traps can be set on GLib by setting the `G_DEBUG` environment variable:
[source,sh]
----
-$ G_DEBUG=fatal_criticals libtool --mode=execute ddd wireshark
+$ G_DEBUG=fatal_criticals ddd wireshark
----
See http://library.gnome.org/devel/glib/stable/glib-running.html[]