[Bug 44594] MindManager Pro v7.0 shows XML processing error on startup (needs support for 'exhaustive-errors', 'external-general-entities' and 'external-parameter-entities' features in MSXML SAX reader)

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=44594

Anastasius Focht <focht at gmx.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|MindManager Pro v7.0        |MindManager Pro v7.0 shows
                   |crashes                     |XML processing error on
                   |                            |startup (needs support for
                   |                            |'exhaustive-errors',
                   |                            |'external-general-entities'
                   |                            |and
                   |                            |'external-parameter-entitie
                   |                            |s' features in MSXML SAX
                   |                            |reader)
         Resolution|---                         |FIXED
                 CC|                            |focht at gmx.net
      Fixed by SHA1|                            |585e12fa9d3fbf3e3460350e445
                   |                            |97d7c0ec18ad2
             Status|NEW                         |RESOLVED
          Component|msxml6                      |msxml3
                URL|                            |https://web.archive.org/web
                   |                            |/20071122165848/http://ftp2
                   |                            |.mindjet.com/download/MM70-
                   |                            |E-429_Pro.exe
           Severity|minor                       |normal

--- Comment #8 from Anastasius Focht <focht at gmx.net> ---
Hello folks,

I've found a stable link via Internet Archive/Wayback machine:

https://web.archive.org/web/20071122165848/http://ftp2.mindjet.com/download/MM70-E-429_Pro.exe

Nikolay's patch from comment #2 was committed here:

https://source.winehq.org/git/wine.git/commitdiff/1d78226f514b3026eea466404afde9bae4e8b72f
("msxml3/saxreader: Accept disabled "exhaustive-errors" property.")    Mon, 26
Feb 2018 

A reworked version of Nikolay's patch from comment #4 was committed here:

https://source.winehq.org/git/wine.git/commitdiff/585e12fa9d3fbf3e3460350e44597d7c0ec18ad2
("msxml3/saxreader: Accept external-general-entities and
external-parameter-entities.") Mon, 26 Feb 2018

-> Part of Wine 3.3

Now it's at a different problem:

--- snip ---
$ pwd
/home/focht/.wine/drive_c/Program Files (x86)/Mindjet/MindManager 7

$ WINEDEBUG=+seh,+relay,+msxml wine ./MindManager.exe >>log.txt 2>&1
...
003c:trace:msxml:isaxxmlreader_putFeature (0x3cbcc08)->(L"exhaustive-errors" 0)
...
003c:trace:msxml:isaxxmlreader_putFeature
(0x3cbcc08)->(L"http://xml.org/sax/features/external-general-entities"
ffffffff)
...
003c:fixme:msxml:isaxxmlreader_putFeature
(0x3cbcc08)->(L"http://xml.org/sax/features/external-general-entities"
ffffffff) stub
...
003c:trace:msxml:isaxxmlreader_putFeature
(0x3cbcc08)->(L"http://xml.org/sax/features/external-parameter-entities"
ffffffff)
...
003c:fixme:msxml:isaxxmlreader_putFeature
(0x3cbcc08)->(L"http://xml.org/sax/features/external-parameter-entities"
ffffffff) stub
...
003c:trace:msxml:isaxxmlreader_putFeature (0x3cbcc08)->(L"schema-validation" 0)
...
003c:trace:msxml:internal_putProperty (0x3cbcc08)->(L"charset" 0x32dc20
{VT_BSTR: L"UTF-8"})
...
003c:fixme:msxml:internal_putProperty (0x3cbcc08)->(L"charset":0x32dc20
{VT_BSTR: L"UTF-8"}): unsupported property
...
003c:Call KERNEL32.GetLastError() ret=022d84c5
003c:Ret  KERNEL32.GetLastError() retval=000036b7 ret=022d84c5
003c:Call
KERNEL32.FormatMessageW(00001300,00000000,000036b7,00000400,00000000,00000000,00000000)
ret=022d84f3
003c:Ret  KERNEL32.FormatMessageW() retval=00000000 ret=022d84f3
...
003c:Call msvcr80.vswprintf_s(03ae09a0,0000000b,023068ec L"0x%08X",0032dc5c)
ret=78306c82
003c:Ret  msvcr80.vswprintf_s() retval=0000000a ret=78306c82
003c:Call ole32.GetErrorInfo(00000000,0032dca0) ret=022d8557
003c:Ret  ole32.GetErrorInfo() retval=00000001 ret=022d8557
003c:Call msvcr80._CxxThrowException(0032dd40,0230ce1c) ret=022e5cc7
003c:Call KERNEL32.RaiseException(e06d7363,00000001,00000003,0032dc64)
ret=7d926935
...
003c:trace:seh:raise_exception code=e06d7363 flags=1 addr=0x7b00dab1
ip=7b00dab1 tid=003c
003c:trace:seh:raise_exception  info[0]=19930520
003c:trace:seh:raise_exception  info[1]=0032dd40
003c:trace:seh:raise_exception  info[2]=0230ce1c
003c:trace:seh:raise_exception  eax=0032dbb4 ebx=0032ea90 ecx=0032dc64
edx=0032dbb4 esi=00000003 edi=0032dc20
003c:trace:seh:raise_exception  ebp=0032dc08 esp=0032dbb4 cs=320023 ds=ffff002b
es=002b fs=f7b90063 gs=006b flags=00000216 
...
003c:Call user32.SetWindowTextW(0001033a,03ae0448 L"XML processing error")
ret=7833abe2 
--- snip ---

We should to draw a line here. Recycling the same bug report over and over
again for different underlying issues is bad - even if they are in same
component and the end-user visible error message/dialog is the same all the
time.

Meta bugs "make app x to work" are rather difficult to handle when it comes to
duplication/sharing it with other apps that don't make use of the same
featureset and/or require only a subset of the changes. It also makes
regression tracking rather hard because people tend to reopen old issues which
doesn't make sense in case of meta bugs (although this can be worked around by
creating new ones, specifically addressing one changeset of the meta-bug).

I will create a continuation bug and link it here.

$ sha1sum MM70-E-429_Pro.exe 
a546bdbad175260764b0a11f250d02950b93e940  MM70-E-429_Pro.exe

$ du -sh MM70-E-429_Pro.exe 
77M    MM70-E-429_Pro.exe

$ wine --version
wine-5.0-rc5

Regards

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.