https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2053
--- Comment #26 from Bill Meier <wmeier@xxxxxxxxxxx> 2008-08-20 12:58:00 PDT ---
(In reply to comment #25)
> I found an easy way to reproduce the crash.
>
> After one or to try, I can reproduce the crash, and with Valgrind, the memory
> corruption is detected. But I was no able to find out where is the bug.
>
Thanks !! using a slight variance of the sequence described consistently
causes my Windows Wireshark to crash.
So far by a process of simplification I seem to have narrowed the problem down
(if I'm not being deceived) to main_widgets_rearrange().
That is: Doing basically just the following during the prefs_main_apply_cb
causes a crash:
prefs_main_fetch_all();
prefs_apply_all();
main_widgets_rearrange();
cf_redissect_packets(): crashes (eventually)
There is no crash if main_widgets_rearrange is not called.
So: I'm studying what goes on during main_widgets_rearrange() ...
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.