Wireshark · Ethereal-dev: RE: [Ethereal-dev] H.225 problem, and running under gdb

[Biot Olivier <Olivier.Biot@xxxxxxxxxxx>]

|From: Martin Mathieson
|
|
|It
|would be good to say something about the use of gdb in 
|README.developer (and
|possibly the website development page?).  I used my nobbled 
|ethereal launch
|script to get to the gdb prompt - do others do this, or 
|perhaps just launch
|ethereal normally then attach to the process before opening 
|making it fail?

The correct way of launching GDB with a shared libethereal is by means of
the libtool script. Depending on the version of libtool, you'd have to say
either:
	$ ./libtool --mode=gdb ./ethereal
or
	$ ./libtool gdb ./ethereal

Note that if you want to pass command-line arguments to ethereal in a GDB
session, you have to write:
	$ ./libtool --mode=gdb --args ./ethereal -r file.cap
or
	$ ./libtool gdb --args ./ethereal -r file.cap

Running Ethereal once GDB started:
	gdb> r

Getting a full backtrace:
	gdb> bt full

Getting a normal backtrace:
	gdb> bt

Kill gdb and quit:
	gdb> q

Hope this helps!

Regards,

Olivier