aCC: error 1922: "/opt/aCC/lbin/ctcom" terminated with signal 10

[Srikrishna Erra]

Hi.
I am afraid about the Compiler behaviour as it behaves strange.

What could be the difference
-- in compiling original cpp code directly
AND
-- compiling cpp code by having its equivalent preprocessed code included in it.


Can i trust the Compiler in this case and proceed futher?


Thanks

regards,
Srikrishna Erra.

[Dennis Handly]

>What could be the difference
>in compiling original cpp code directly
>compiling cpp code by having its equivalent preprocessed code included in it.

Possibly different heap layout in the compiler.

>Can I trust the compiler in this case and proceed further?

You don't really have much of a choice unless you update the compiler.

I assume you have way to test your changes?

[Srikrishna Erra]

Hi,
I had found the root cause of this issue.

My configure script assuming UTF16 string literal support is provided by the compier used i.e. passing UTF16 strings like u"Stringliteral" but it seems the compiler(aCC 05.50) i am using is not supporting above kind of string literals.

Issue is with my Configure script. The script is not checking whether it is supported or not. It simply assuming the support is existed and passing string literals in the above form.

I just need confirmation for
Does Compiler (aCC 05.05) really not supports UTF16 String literals or should "install any patch/do any changes" to get the support?

Thanks

regadrs,
Srikrishna Erra.

[Dennis Handly]

>i.e. passing UTF16 strings like u"Stringliteral" but it seems the compiler (A.05.50) is not supporting above kind of string literals.

This should be supported as long as the chars are ascii.

>Does compiler (A.05.50) really not supports UTF16 String literals

It should provide limited support for them.

>or should "install any patch/do any changes" to get the support?

A.05.36 thru A.05.41 abort. Perhaps your "prerelease" A.05.50 doesn't have the fix?

Well, you could always go to the latest, A.06.25.01.