Wireshark-bugs: [Wireshark-bugs] [Bug 4620] New: OutputDebugString calls must not be present in
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Fri, 26 Mar 2010 08:58:27 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4620

           Summary: OutputDebugString calls must not be present in release
                    software
           Product: Wireshark
           Version: 1.2.5
          Platform: x86-64
        OS/Version: Windows 7
            Status: NEW
          Severity: Major
          Priority: Low
         Component: Wireshark
        AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
        ReportedBy: jaltman@xxxxxxxxxxxxxxxxxxxx


Build Information:
wireshark 1.2.5 (SVN Rev 31296)

Copyright 1998-2009 Gerald Combs <gerald@xxxxxxxxxxxxx> and contributors.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Compiled with GTK+ 2.16.2, with GLib 2.20.3, with WinPcap (version unknown),
with libz 1.2.3, without POSIX capabilities, without libpcre, without SMI,
without c-ares, without ADNS, with Lua 5.1, without GnuTLS, without Gcrypt,
without Kerberos, without GeoIP, with PortAudio V19-devel (built Dec 17 2009),
with AirPcap.
NOTE: this build doesn't support the "matches" operator for Wireshark filter
syntax.

Running on 64-bit Windows 7, build 7600, with WinPcap version 4.1.1 (packet.dll
version 4.1.0.1753), based on libpcap version 1.0 branch 1_0_rel0b (20091008),
without AirPcap.

Built using Microsoft Visual C++ 9.0 build 30729
--
WireShark issues OutputDebugString calls during normal operation.  For example
when evaluating interface and when receiving packets and ....

OutputDebugString requires the acquisition of a system-wide mutex and can
result in severe performance degradation of the entire Windows operating
system.  Please remove all calls to OutputDebugString from release builds of
Wireshark.

For background information on how OutputDebugString is implemented within
Windows, see http://www.unixwiz.net/techtips/outputdebugstring.html

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