https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=7498
Bill Meier <wmeier@xxxxxxxxxxx> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution| |FIXED
--- Comment #10 from Bill Meier <wmeier@xxxxxxxxxxx> 2012-07-29 11:41:42 PDT ---
KH:
I found that a crash occurred if I enabled the NFS "file_name_snooping" &
"file_full_name_snooping" preferences.
I have committed a fix for that problem in SVN #44111.
The issue: Memory beyond the end of a buffer was being overwritten when a "file
full name" was being generated.
Since the buffer was allocated in dynamic memory (the heap), the actual
crash/symptom would vary depending upon the exact sequence of memory
allocation.
You can try the fix by downloading a development Wireshark with filename
Wireshark-win32-1.9.0-SVN-44111.exe or later from
http://www.wireshark.org/download/automated/win32.
(This file is generated by an automated process and should appear in the
directory shortly).
I'm going close this bug assuming that you had these two NFS preferences
enabled and that the bug I've fixed is the one you encountered.
If you did not have these preferences enabled or you find that you still
encounter crashes, please fee free to re-open the bug.
Also, I'll queue this fix to be backported to the next Wireskark 1.4, 1.6 & 1.8
releases.
Thanks for the bug report...
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
