Wireshark · Wireshark-bugs: [Wireshark-bugs] [Bug 4402] New: PDML output from TShark includes invalid characters

[bugzilla-daemon@xxxxxxxxxxxxx]

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

           Summary: PDML output from TShark includes invalid characters
           Product: Wireshark
           Version: 1.2.5
          Platform: x86
        OS/Version: Windows XP
            Status: NEW
          Severity: Normal
          Priority: Low
         Component: TShark
        AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
        ReportedBy: shulman@xxxxxxxxxxx


Build Information:
TShark 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 GLib 2.20.3, with WinPcap (version unknown), with libz 1.2.3,
without POSIX capabilities, with libpcre 7.0, with SMI 0.4.8, with c-ares
1.6.0,

with Lua 5.1, with GnuTLS 2.8.1, with Gcrypt 1.4.4, with MIT Kerberos, with
GeoIP.

Running on Windows XP Service Pack 3, build 2600, with WinPcap version 4.1.1
(packet.dll version 4.1.0.1753), based on libpcap version 1.0 branch 1_0_rel0b
(20091008), GnuTLS 2.8.1, Gcrypt 1.4.4.

Built using Microsoft Visual C++ 9.0 build 30729
--
When I use TShark to create PDML files from capture files non-ASCII byte codes
are copied as-is into the output xml file yielding it invalid. The same
operation when peformed from within Wireshark's GUI yields a valid file in
which the non-standard byte code is replaced with an escaped notation (e.g.
\x97).
I've noticed this in the "show" attribute of HTTP protocol fields.

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