Wireshark-bugs: [Wireshark-bugs] [Bug 3902] New: Can not parse WBXML completely

Date: Sun, 16 Aug 2009 19:42:41 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3902

           Summary: Can not parse WBXML completely
           Product: Wireshark
           Version: 1.1.x (Experimental)
          Platform: x86
        OS/Version: Windows 2000
            Status: ASSIGNED
          Severity: Normal
          Priority: Medium
         Component: Wireshark
        AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
        ReportedBy: ziqiao.xu@xxxxxxxxxx
                CC: ziqiao.xu@xxxxxxxxxx


Created an attachment (id=3520)
 --> (https://bugs.wireshark.org/bugzilla/attachment.cgi?id=3520)
The trace of this PR

Build Information:
Version 1.1.1 (SVN Rev 26391)

Copyright 1998-2008 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.14.3, with GLib 2.18.1, 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.5.3, without ADNS, with Lua 5.1, with GnuTLS 2.3.8, with Gcrypt
1.4.1, with MIT Kerberos, with PortAudio V19-devel (built Oct  8 2008), with
AirPcap.

Running on Windows 2000 Service Pack 4, build 2195, with WinPcap version 4.0.2
(packet.dll version 4.0.0.1040), based on libpcap version 0.9.5, without
AirPcap.

Built using Microsoft Visual C++ 9.0 build 30729

Wireshark is Open Source Software released under the GNU General Public
License.

Check the man page and http://www.wireshark.org for more information.
--
When I access an un-existed URL by Mobile under an WSP proxy, in a normal
condition, that proxy will return an code like 735 to indicate that the request
is time-out. But it return some unreadabel characters, from the Trace I caught
by Wireshark, i find one of the WBXML was decoded as like following:
[truncated]     2 | Tag   | T   0    | STR_I (Inline string)           |     
'\346\237\343\203\250\257\343\210\243\257\343\203\247\275\221\347\273\224\231\347\232\204IP\345\234\346\235\277\235\200\346\276\266\350\276\253\350\247\246\351\2

Seems that Inline string is not decoded compeleted. Is it Wireshark's problem?


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