<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">Hi Prasath<br>
      <br>
      You mentioned that in order to compile omniORB with c++17 option
      you have removed the 'throw' <br>
      specifications from some functions declarations. How did you
      actually do that? Could it be <br>
      that you have made this modification in the following way:<br>
      <br>
          void f() throw (BadParam)   =&gt; void f() throw () <br>
      <br>
      The crash which you get normally happens in one of the two cases:<br>
      <br>
       1) A function declares 'throw(A)' but actually throws a different
      exception 'B'.<br>
       2) A function is declared as not throwing any exception using
      'throw()' declaration but actually throws an exception.<br>
      <br>
      So I would suggest you to check that you have removed the
      'throw(...)' specifications completely<br>
      from all the functions concerned and don't have 'throw()' terms
      left anywhere in these functions <br>
      declarations.<br>
      <br>
      Cheers,<br>
      Serguei<br>
      <br>
      On 4/23/19 11:01 AM, Prasath via omniORB-list wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:MWHP102MB00953EC14A92ABF91222E455EB230@MWHP102MB0095.NAMP102.PROD.OUTLOOK.COM">
      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
      <meta name="Generator" content="Microsoft Exchange Server">
      <!-- converted from rtf -->
      <style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
      <font size="2" face="Calibri"><span style="font-size:11pt;">
          <div>Hi Duncan, </div>
          <div> </div>
          <div>Thanks for the response. </div>
          <div> </div>
          <div>Please find the answers below,</div>
          <div> </div>
          <div><font color="#833C0B"><b>Where did the compiler come
                from?  </b></font></div>
          <div><font face="Calibri">gcc 8.2 (gcc-8.2.0.tar.gz) is
              downloaded from <a href="https://gcc.gnu.org/"
                moz-do-not-send="true"><font color="#0563C1"><u>https://gcc.gnu.org/</u></font></a>
            </font></div>
          <div><font color="#833C0B"> </font></div>
          <div><font color="#833C0B"><b>Did you compile it yourself?  </b></font></div>
          <div>Yes, we compiled it (<font face="Calibri">gcc-8.2.0.tar.gz</font>).
            Arguments to gcc configure script below,</div>
          <div>$./configure
            --prefix=/usr/local/gcc-8.2-powerpc-ibm-aix6.1.0.0
            --build=powerpc-ibm-aix6.1.0.0 --without-gnu-as
            --with-as=/usr/bin/as --without-gnu-ld --with-ld=/usr/bin/ld
            --disable-nls --disable-shared --enable-languages=c++
            --enable-checking=release
            --enable-bootstrap -enable-version-specific-runtime-libs</div>
          <div>$make install</div>
          <div> </div>
          <div><font color="#833C0B"><b>What does "g++ -v" report?</b></font></div>
          <div>bash-4.4$ ./g++ -v</div>
          <div>Using built-in specs.</div>
          <div>COLLECT_GCC=./g++</div>
          <div>COLLECT_LTO_WRAPPER=/usr/local/gcc-8.2-powerpc-ibm-aix6.1.0.0/libexec/gcc/powerpc-ibm-aix6.1.0.0/8.2.0/lto-wrapper</div>
          <div>Target: powerpc-ibm-aix6.1.0.0</div>
          <div>Configured with:
            /disks/smithers3/workplaces/build/gcc-8.2/gcc-8.2.0/configure
            --prefix=/usr/local/gcc-8.2-powerpc-ibm-aix6.1.0.0
            --build=powerpc-ibm-aix6.1.0.0 --without-gnu-as
            --with-as=/usr/bin/as --without-gnu-ld --with-ld=/usr/bin/ld
            --disable-nls
            --disable-shared --enable-languages=c++
            --enable-checking=release --enable-bootstrap
            -enable-version-specific-runtime-libs</div>
          <div>Thread model: aix</div>
          <div>gcc version 8.2.0 (GCC)</div>
          <div> </div>
          <div><font color="#833C0B"><b>How did you configure omniORB? 
                What were the arguments to its configure script?</b></font></div>
          <div>$./configure --prefix=/usr/local/dev</div>
          <div>$make</div>
          <div>$make install</div>
          <div> </div>
          <div>As per your advice, we removed all the throw
            specifications and it got compiled successfully.</div>
          <a name="_MailEndCompose" moz-do-not-send="true"></a>
          <div>And tested again but we are getting the same termination.
            For your reference, I have attached the completed log (it
            also has crash stack) with this mail.</div>
          <div> </div>
          <div>Please provide your thoughts to proceed further.</div>
          <div> </div>
          <div>Thanks &amp; Regards,</div>
          <div>P. Prasath. </div>
          <div> </div>
          <div>-----Original Message-----<br>
            From: Duncan Grisby <a class="moz-txt-link-rfc2396E" href="mailto:duncan@grisby.org">&lt;duncan@grisby.org&gt;</a> <br>
            Sent: Tuesday, April 16, 2019 5:58 PM<br>
            To: Prasath Palaniappan
            <a class="moz-txt-link-rfc2396E" href="mailto:Prasath_Palaniappan@amat.com">&lt;Prasath_Palaniappan@amat.com&gt;</a>;
            <a class="moz-txt-link-abbreviated" href="mailto:omniorb-list@omniorb-support.com">omniorb-list@omniorb-support.com</a><br>
            Cc: Shankar Chinnusamy <a class="moz-txt-link-rfc2396E" href="mailto:Shankar_Chinnusamy@amat.com">&lt;Shankar_Chinnusamy@amat.com&gt;</a><br>
            Subject: Re: [omniORB] [External] Re: OmniORB-4.2.2 compiled
            with gcc8 and C++14 leads into crash</div>
          <div> </div>
          <div> </div>
          <div>CAUTION: EXTERNAL EMAIL. Verify before you click links or
            open attachments. Questions? Contact GIS.</div>
          <div> </div>
          <div> </div>
          <div> </div>
          <div>On Wed, 2019-04-10 at 11:03 +0000, Prasath via
            omniORB-list wrote:</div>
          <div> </div>
          <div>&gt; OmniORB-4.2.2 has dynamic exception specifications
            those are </div>
          <div>&gt; unsupported in C++17.</div>
          <div>&gt; So we removed those unsupported dynamic exception
            specifications and </div>
          <div>&gt; compiled the OmniORB-4.2.2 with "gcc8 and C++17".</div>
          <div>&gt; virtual void visit(const char* value,Source source)
            throw (BadParam) = </div>
          <div>&gt; 0;</div>
          <div> </div>
          <div>Yes, that is the right thing to do. Just remove all the
            throw specifications. The only place that has those throw
            specifications is in the option processing code, which is
            not involved at all in the errors you are seeing. Whatever
            the problem is, it has
            absolutely nothing to do with those throw specifications.</div>
          <div> </div>
          <div>&gt; Apart from those changes what else need to be done
            to compile the</div>
          <div>&gt; OmniORB-4.2.2 with "gcc8 and C++17" properly?</div>
          <div> </div>
          <div>Nothing. It works fine with just that change.</div>
          <div> </div>
          <div>&gt; Clarifications:</div>
          <div>&gt; As you mentioned that you have removed throw
            specifications in</div>
          <div>&gt; OmniORB-4.3 to support future compilers and it is in
            development </div>
          <div>&gt; branch. If so, could you please let us know when it
            will be released?</div>
          <div> </div>
          <div>There is no current timeframe for omniORB 4.3 to be
            released, but that is irrelevant here. There are no other
            changes in 4.3 that are related to this.</div>
          <div> </div>
          <div>The compiler has generated incorrect code, or the C++
            runtime is faulty. An exception is being thrown but it not
            being caught as it should be by the exception handler.</div>
          <div> </div>
          <div>Where did the compiler come from?  Did you compile it
            yourself?  What does "g++ -v" report?</div>
          <div> </div>
          <div>How did you configure omniORB?  What were the arguments
            to its configure script?</div>
          <div> </div>
          <div>Duncan.</div>
          <div> </div>
          <div>--</div>
          <div> -- Duncan Grisby         --</div>
          <div>  -- <a href="mailto:duncan@grisby.org"
              moz-do-not-send="true">duncan@grisby.org</a>     --</div>
          <div>   -- <a href="http://www.grisby.org"
              moz-do-not-send="true">http://www.grisby.org</a> --</div>
          <div> </div>
          <div><font face="Calibri">The content of this message is
              APPLIED MATERIALS CONFIDENTIAL. If you are not the
              intended recipient, please notify me, delete this email
              and do not use or distribute this email. </font></div>
        </span></font>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <pre class="moz-quote-pre" wrap="">_______________________________________________
omniORB-list mailing list
<a class="moz-txt-link-abbreviated" href="mailto:omniORB-list@omniorb-support.com">omniORB-list@omniorb-support.com</a>
<a class="moz-txt-link-freetext" href="http://www.omniorb-support.com/mailman/listinfo/omniorb-list">http://www.omniorb-support.com/mailman/listinfo/omniorb-list</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>