[
https://issues.apache.org/jira/browse/XERCESC-2173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16899133#comment-16899133
]
Roger Leigh commented on XERCESC-2173:
--------------------------------------
The stack trace isn't too useful as is--it's not possible to see exactly where
the error occurred. There are a few overloaded methods for loadMsg, and it's
not clear which was at fault, or where. Please could you repeat with a Debug
build?
Looking at where the fault might be triggered, the most likely candidate is the
transcoder. It might be worth trying an alternative one. The ICU, GNU iconv
and MacOS transcoders all use a mutex.
The fault is in locking a critical section, and it looks like you're using
VS2013. I have a vague recollection that I've seen this issue before, and that
it's a bug in the MSVC runtime. I'm certainly not seeing any problems of this
nature with VS2015, VS2017 or VS2019. Part of the problem might be in
creating/locking the mutex during the final stages of process shutdown.
I hope that provides some pointers.
> Application crashes with an error as "A wrong parameter was passed to a
> service or function"
> --------------------------------------------------------------------------------------------
>
> Key: XERCESC-2173
> URL: https://issues.apache.org/jira/browse/XERCESC-2173
> Project: Xerces-C++
> Issue Type: Bug
> Components: Utilities
> Affects Versions: 3.2.2
> Environment: Windows
> Reporter: Samrin
> Priority: Critical
> Attachments: Crash_Call_Stack.png
>
>
> Hi All,
> We have an application which uses the latest xerces C++ 3.2.2 version. Upon
> running the application when we press CTRL+C it crashes leading to error
> message as "A wrong parameter was sent to service or function". This error
> message is thrown in ntdll.dll file.
> The call stack is attached for reference. Any help would be appreciated.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
