[ 
https://issues.apache.org/jira/browse/XERCESC-2174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16898288#comment-16898288
 ] 

Roger Leigh commented on XERCESC-2174:
--------------------------------------

It's not going to be clear what is going on here without a bit of investigation.

I would suggest starting by installing gdb in the container, and then running 
the command specified in the shell script within gdb, then get a backtrace when 
the segfault happens.  This should show exactly where the segfault occurs.

All the Linux CI builds test building with Ubuntu in a docker image (trusty).  
We should probably update it to use a newer version.  But I don't see any 
reason for it to fail in Docker or on Ubuntu; it should work on every version 
without trouble.

>  xerces-c runs make check in linux, most of the results about Threadtest test 
> case display fail.
> ------------------------------------------------------------------------------------------------
>
>                 Key: XERCESC-2174
>                 URL: https://issues.apache.org/jira/browse/XERCESC-2174
>             Project: Xerces-C++
>          Issue Type: Test
>            Reporter: Smart Yang
>            Priority: Minor
>
> Dear author,
> I have a question about Threadtest test
> When I ran the test case on Ubuntu 16.04.2, most of the Threadtest test cases 
> failed. When I looked at test-suit.log, I found the error message is the 
> same: “../scripts/run-test: line 8 : 121998 Segmentation fault (core dumped) 
> "${top_builddir}/$cmd" "$@" $input > "$output" 2> "$output" ”
> I executed the use case in the docker Ubuntu 16.04.2 image, and the 
> Threadtest test case passed.
> The reason why this Threadtest test case fails is caused by the test 
> environment or other reasons?



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org
For additional commands, e-mail: c-dev-h...@xerces.apache.org

Reply via email to