Follow Techotopia on Twitter

On-line Guides
All Guides
eBook Store
iOS / Android
Linux for Beginners
Office Productivity
Linux Installation
Linux Security
Linux Utilities
Linux Virtualization
Linux Kernel
System/Network Admin
Programming
Scripting Languages
Development Tools
Web Development
GUI Toolkits/Desktop
Databases
Mail Systems
openSolaris
Eclipse Documentation
Techotopia.com
Virtuatopia.com

How To Guides
Virtualization
General System Admin
Linux Security
Linux Filesystems
Web Servers
Graphics & Desktop
PC Hardware
Windows
Problem Solutions

  




 

 

3.8. Make changes to the Wireshark sources

As the Wireshark developers are working on many different platforms, a lot of editors are used to develop Wireshark (emacs, vi, Microsoft Visual Studio and many many others). There's no "standard" or "default" development environment.

There are several reasons why you might want to change the Wireshark sources:

  • add your own new dissector

  • change/extend an existing dissector

  • fix a bug

  • implement a new glorious feature :-)

The internal structure of the Wireshark sources will be described in Part II, “Wireshark Development (incomplete)”.

[Tip] Tip!

Ask the developer mailing list before you really start a new development task. If you have an idea what you want to add/change, it's a good idea to contact the developer mailing list (see Section 1.7.5, “Mailing Lists”) and explain your idea. Someone else might already be working on the same topic, so double effort can be reduced, or someone can give you some tips that should be thought about (like side effects that are sometimes very hard to see).


 
 
  Published under the terms fo the GNU General Public License Design by Interspire