Wireshark

  • Riverbed Technology
  • WinPcap
the world's foremost network protocol analyzer
  • Wireshark
    • About
    • Download
    • Blog
  • Get Help
    • Ask a Question
    • FAQs
    • Documentation
    • Mailing Lists
    • Online Tools
    • Wiki
    • Bug Tracker
  • Develop
    • Get Involved
    • Developer's Guide
    • Browse the Code
    • Latest Builds

Wireshark-bugs: [Wireshark-bugs] [Bug 2164] Packet dissector showing bogus errors in jabber packets

Date Index Thread Index Other Months All Mailing Lists
Date Prev Date Next Thread Prev Thread Next


From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Fri, 4 Jan 2008 08:40:48 +0000 (GMT)

http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2164





------- Comment #1 from marco.ullasci@xxxxxxxxx  2008-01-04 08:40 GMT -------
Created an attachment (id=1340)
 --> (http://bugs.wireshark.org/bugzilla/attachment.cgi?id=1340&action=view)
Capture showing the problem


-- 
Configure bugmail: http://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

  • References:
    • [Wireshark-bugs] [Bug 2164] New: Packet dissector showing bogus errors in jabber packets
      • From: bugzilla-daemon
  • Prev by Date: [Wireshark-bugs] [Bug 2164] New: Packet dissector showing bogus errors in jabber packets
  • Next by Date: [Wireshark-bugs] [Bug 2162] for() loop evaluation order in ep_strndup() can trigger valgrind "invalid read of size 1"
  • Previous by thread: [Wireshark-bugs] [Bug 2164] New: Packet dissector showing bogus errors in jabber packets
  • Next by thread: [Wireshark-bugs] [Bug 2165] New: Regression on decoding H248
  • Index(es):
    • Date
    • Thread

Wireshark and the "fin" logo are registered trademarks of the Wireshark Foundation