[bugzilla-daemon@xxxxxxxxxxxxx]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=6695

Bill Meier <wmeier@xxxxxxxxxxx> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|FIXED                       |WONTFIX

--- Comment #2 from Bill Meier <wmeier@xxxxxxxxxxx> 2012-02-23 21:29:31 PST ---
Reverted in SVN #41168

Reason: Use of g_fprintf(std..., ...) fails (crashes) on Windows for Wireshark
executables built with VC2008 (or any VC newer than VC6).

It appears that Windows GLib from the package we use is linked with (depends
on) MSVCRT (Microsoft C Runtime).

Wireshark is linked with a different version of the C Runtime: MSVCR90 (or
whatever depending upon the version of MSVC used to build Wireshark).

Therefore using g_fprintf() (and similar) on Windows is a non-starter.

Basically: the FILE *std... referenced in the call to g_fprintf(std..., ...)
will be from the MSVCR90 C runtime while the actual g_fprintf() code in LIBGLIB
will try to use the file handle in the MSVCRT C runtime.

Extract from Windows 'depends' output for editcap.exe

 ...\wireshark\ws\wsh-svn\wireshark-gtk2\EDITCAP.EXE
     ...
      ...\wireshark\ws\wsh-svn\wireshark-gtk2\WIRETAP-1.7.0.DLL
      ...\wireshark\ws\wsh-svn\wireshark-gtk2\LIBWSUTIL.DLL
      ...\wireshark\ws\wsh-svn\wireshark-gtk2\LIBGLIB-2.0-0.DLL
           ...
           c:\windows\system32\MSVCRT.DLL
           ...
      ...\wireshark\ws\wsh-svn\wireshark-gtk2\LIBGMODULE-2.0-0.DLL
           ...
      c:\windows\winsxs\...\MSVCR90.DLL


So: I'm marking this as "WONTFIX".

Thanks anyway for the effort ....

-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.