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

Chuck Rolke commented on PROTON-1156:
-------------------------------------

terminus.cpp will compile with an unacceptable code change but then the ICE 
moves to some other module. 
{noformat}
-terminus::terminus(pn_terminus_t* t) :
-    object_(t), properties_(pn_terminus_properties(t)), 
filter_(pn_terminus_filter(t))
-{}
+terminus::terminus(pn_terminus_t* t)
+{   object_ = t;
+    properties_ = pn_terminus_properties(t);
+    filter_ = pn_terminus_filter(t);
+}
{noformat}

This code has been around for a while and the error is probably a result of 
changes to included files.

I'm all for retiring VS2008 support. Do we call for a vote?

> Building C++ binding causes VS2008 to ICE
> -----------------------------------------
>
>                 Key: PROTON-1156
>                 URL: https://issues.apache.org/jira/browse/PROTON-1156
>             Project: Qpid Proton
>          Issue Type: Bug
>          Components: cpp-binding
>    Affects Versions: 0.13.0
>         Environment: Windows Visual Studio 2008 (VS9)
>            Reporter: Andrew Stitcher
>            Assignee: Cliff Jansen
>
> {noformat}
> 3>c:\jenkins\workspace\proton-c-master-windows\rh-qpid-proton\proton-c\bindings\cpp\src\terminus.cpp(29)
>  : fatal error C1001: An internal error has occurred in the compiler.
> 3>(compiler file 
> 'f:\dd\vctools\compiler\utc\src\p2\main.c[0x6C510CA6:0x00000010]', line 182)
> 3> To work around this problem, try simplifying or changing the program near 
> the locations listed above.
> 3>Please choose the Technical Support command on the Visual C++ 
> 3> Help menu, or open the Technical Support help file for more information
> 3>Internal Compiler Error in C:\Program Files\Microsoft Visual Studio 
> 9.0\VC\bin\cl.exe.  You will be prompted to send an error report to Microsoft 
> later.
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to