http://bugs.winehq.org/show_bug.cgi?id=36467
Bug ID: 36467 Summary: wine demangle bug Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msvcrt Assignee: wine-bugs@winehq.org Reporter: christopherwuy@gmail.com
1.The symbol: put@?$num_put@DV?$ostreambuf_iterator@DU?$char_traits@D@std@@@std@@@std@@QBE?AV?$ostreambuf_iterator@DU?$char_traits@D@std@@@2@V32@AAV 2.The correct result in Windows vs2008 undname public: class std::ostreambuf_iterator<char,struct std::char_traits<char> > __thiscall std::num_put<char,class std::ostreambuf_iterator<char,struct std::char_traits<char> > >::put(class std::ostreambuf_iterator<char,struct std::char_traits<char> >,class ?? &, ?? )const throw( ?? ) 3.The wrong result in Wine put@num_put<char,class std::ostreambuf_iterator<char,struct std::char_traits<char> > >
http://bugs.winehq.org/show_bug.cgi?id=36467
Piotr Caban piotr.caban@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |piotr.caban@gmail.com
--- Comment #1 from Piotr Caban piotr.caban@gmail.com --- The mangled name you have pasted here is broken (native demangler behaves the same way as wine on it). Please update the bug with different mangled name (that behaves differently on wine and windows). You can also mark it as invalid if it was caused by some kind of mistake.
I don't think it's useful to make our implementation behave identically as native on broken data unless something depends on it.
http://bugs.winehq.org/show_bug.cgi?id=36467
--- Comment #2 from christopherwuy@gmail.com --- (In reply to christopherwuy from comment #0)
1.The symbol: put@?$num_put@DV?$ostreambuf_iterator@DU?$char_traits@D@std@@@std@@@std@@QBE? AV?$ostreambuf_iterator@DU?$char_traits@D@std@@@2@V32@AAV 2.The correct result in Windows vs2008 undname public: class std::ostreambuf_iterator<char,struct std::char_traits<char> > __thiscall std::num_put<char,class std::ostreambuf_iterator<char,struct std::char_traits<char> > >::put(class std::ostreambuf_iterator<char,struct std::char_traits<char> >,class ?? &, ?? )const throw( ?? ) 3.The wrong result in Wine put@num_put<char,class std::ostreambuf_iterator<char,struct std::char_traits<char> > >
The second one:
1.The symbol: ?do_put@?$num_put@DV?$ostreambuf_iterator@DU?$char_traits@D@std@@@std@@@std@@MBE?AV?$ostreambuf_iterator@DU?$char_traits@D@std@@@2@V32@" 2.The correct result in Windows vs2008 undname: protected: virtual class std::ostreambuf_iterator<char,struct std::char_traits<char> > __thiscall std::num_put<char,class std::ostreambuf_iterator<char,struct std::char_traits<char> > >::do_put(class std::ostreambuf_iterator<char,struct std::char_traits<char> >, ?? )const throw( ?? ) 3.The wrong result in Wine: ?do_put@?$num_put@DV?$ostreambuf_iterator@DU?$char_traits@D@std@@@std@@@std@@MBE?AV?$ostreambuf_iterator@DU?$char_traits@D@std@@@2@V32@"
http://bugs.winehq.org/show_bug.cgi?id=36467
christopherwuy@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID
--- Comment #3 from christopherwuy@gmail.com --- (In reply to Piotr Caban from comment #1)
The mangled name you have pasted here is broken (native demangler behaves the same way as wine on it). Please update the bug with different mangled name (that behaves differently on wine and windows). You can also mark it as invalid if it was caused by some kind of mistake.
I don't think it's useful to make our implementation behave identically as native on broken data unless something depends on it.
I ' m terribly sorry! I made a copy & paste mistake.
--- Comment #4 from christopherwuy@gmail.com --- (In reply to Piotr Caban from comment #1)
The mangled name you have pasted here is broken (native demangler behaves the same way as wine on it). Please update the bug with different mangled name (that behaves differently on wine and windows). You can also mark it as invalid if it was caused by some kind of mistake.
I don't think it's useful to make our implementation behave identically as native on broken data unless something depends on it.
I ' m terribly sorry! I made a copy & paste mistake.
http://bugs.winehq.org/show_bug.cgi?id=36467
christopherwuy@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID
--- Comment #3 from christopherwuy@gmail.com --- (In reply to Piotr Caban from comment #1)
The mangled name you have pasted here is broken (native demangler behaves the same way as wine on it). Please update the bug with different mangled name (that behaves differently on wine and windows). You can also mark it as invalid if it was caused by some kind of mistake.
I don't think it's useful to make our implementation behave identically as native on broken data unless something depends on it.
I ' m terribly sorry! I made a copy & paste mistake.
--- Comment #4 from christopherwuy@gmail.com --- (In reply to Piotr Caban from comment #1)
The mangled name you have pasted here is broken (native demangler behaves the same way as wine on it). Please update the bug with different mangled name (that behaves differently on wine and windows). You can also mark it as invalid if it was caused by some kind of mistake.
I don't think it's useful to make our implementation behave identically as native on broken data unless something depends on it.
I ' m terribly sorry! I made a copy & paste mistake.
https://bugs.winehq.org/show_bug.cgi?id=36467
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #5 from Austin English austinenglish@gmail.com --- Closing.
-
wine-bugs＠winehq.org