diff options
| author | Gilbert Ramirez <gram@alumni.rice.edu> | 1999-08-20 04:07:09 +0000 |
|---|---|---|
| committer | Gilbert Ramirez <gram@alumni.rice.edu> | 1999-08-20 04:07:09 +0000 |
| commit | 49388049d3cfae3d5ad1ec260a917bf9737f3c71 (patch) | |
| tree | a590141373494da37deeaaa399ad07c1343ac588 /README | |
| parent | aae22bd2279292449e74a10b6887b034a3b17a78 (diff) | |
| download | wireshark-49388049d3cfae3d5ad1ec260a917bf9737f3c71.tar.gz wireshark-49388049d3cfae3d5ad1ec260a917bf9737f3c71.tar.bz2 wireshark-49388049d3cfae3d5ad1ec260a917bf9737f3c71.zip | |
Made iptrace wiretap module return error on partial packets, instead of
expecting it as normal. Added paragraph about iptrace oddities to README.
I also added a section to the README about how to report bugs.
svn path=/trunk/; revision=519
Diffstat (limited to 'README')
| -rw-r--r-- | README | 37 |
1 files changed, 37 insertions, 0 deletions
@@ -74,6 +74,17 @@ libpcap, Sniffer (uncompresed), NetXray, Sniffer Pro, snoop, Shomiti, LANalyzer, Network Monitor, iptrace 2.0 (AIX), and RADCOM's WAN/LAN Analyzer +Although Ethereal can read AIX iptrace files, the documentation on +AIX's iptrace packet-trace command is sparse. The 'iptrace' command +starts a daemon which you must kill in order to stop the trace. Through +experimentation it appears that sending a HUP signal to that iptrace +daemon causes a graceful shutdown and a complete packet is written +to the trace file. If a partial packet is saved at the end, Ethereal +will complain when reading that file, but you will be able to read all +other packets. If this occurs, please let the Ethereal developers know +at ethereal-dev@zing.org, and be sure to send us a copy of that trace +file if it's small and contains non-sensitive data. + IPv6 ---- @@ -100,6 +111,32 @@ library but _do not_ want to have ethereal use it, you can run configure with the "--disable-snmp" option. No SNMP support will be compiled into ethereal with this option. +How to Report a Bug +------------------- +Ethereal is still under constant development, so it is possible that you will +encounter a bug while using it. Please report bugs to ethereal-dev@zing.org. +Be sure you tell us: + + 1) Operating System and version + 2) Version of GTK+ (the command 'gtk-config --version' will tell you) + 3) The command you used to invoke Ethereal + +If the bug is produced by a particular trace file, please be sure to send +a trace file along with your bug description. Please don't send a trace file +greather than 1MB when compressed. If the trace file contains sensitive +information (e.g., passwords), then please do not send it. + +If Ethereal died on you with a 'segmentation violation', you can help the +developers a lot if you have your debugger installed. A stack trace using +your debugger ('gdb' in this example), the ethereal binary, and the +resulting core file can be obtained by starting the debugger and using +the 'backtrace' command. + +$ gdb ethereal core +> backtrace +..... prints the stack trace +> quit + Disclaimer ---------- |