https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5831
Chris Maynard <christopher.maynard@xxxxxxxxx> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |DUPLICATE
--- Comment #2 from Chris Maynard <christopher.maynard@xxxxxxxxx> 2011-04-14 13:01:51 PDT ---
(In reply to comment #1)
> A number of fixes have been put in to help avoid this type of problem, but I'm
> not sure if they all made it to 1.4.x. Can you try the latest (development)
> version of Wireshark to see if this problem still exists? It's available on
> http://www.wireshark.org/ under download -> development release (1.5.1).
I unintentionally forgot to schedule the fix to be backported to 1.4.x. It's
scheduled for backporting now, but may have just missed the cut for 1.4.5. If
so, look for it in 1.4.6. Since the original bug 1671 was filed against
0.99.6, I scheduled the bug fix to be backported to 1.2.x as well.
*** This bug has been marked as a duplicate of bug 1671 ***
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.