https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3046
Chris Maynard <christopher.maynard@xxxxxxxxx> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
Resolution| |FIXED
--- Comment #27 from Chris Maynard <christopher.maynard@xxxxxxxxx> 2011-12-01 12:50:24 PST ---
(In reply to comment #26)
> The patch attached to this bug ("Call cf_close() in cf_open() instead of
> cf_callback_invoke()+cf_reset_state") does not fix the problem and is not
> committed as of trunk-1.6 r40063. Why is it marked resolved?
As comment 21 indicates, the bug has been fixed and is scheduled for 1.6.5 (and
1.4.11). Typically what happens is just before Gerald decides to release them,
he'll back-port all the bug fixes on the roadmap[1] to the 1.6 and 1.4 trunks.
[1] http://wiki.wireshark.org/Development/Roadmap
> It does not fix the problem. The scenario outlined in Bug 6639 does not hang
> but it does not perform correctly. That is:
>
> 1. wireshark.exe in.pcap
> 2. Ctrl+Shift+s foo.pcap overwrite yes
> --> used to hang. Now does not hang but titlebar says foo.pcap but the window
> still shows the startup screen instead of the list of packets.
OK, but now you are describing a different problem, not the one that you
originally reported in bug 6639.
If you need to reopen bug 6639 as a *different* problem than this one, then go
ahead and do so but please change the title to accurately reflect the nature of
the problem and please update the problem description as well. Or it might be
clearer/simpler to just open a new bug.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
You are watching all bug changes.
