Re: Pro*C/cc executable causes coredump

From: <Steve_Dunn_at_mail.amsinc.com>
Date: 1997/08/09
Message-ID: <33ecbf76.1886481_at_nnrp.crl.com>#1/1


On Wed, 06 Aug 1997 21:50:27 -0500, "John A. Kroll" <krollj_at_worldnet.att.net> wrote:

Thanks for your response John, but we found the problem. Seems that the default cc that comes with SunOS is a link to ucbcc. When we switched to Sun Workshop cc, the problem went away. When I have time, I will find out the differences between the two compilers and the exact reason for the problem. If Sun does have a patch as you mentioned, perhaps it will fix the problem with the ucbcc compiler.

Thanks again,
Steve D.

>Steve_Dunn_at_mail.amsinc.com wrote:
>
>> Anyone, please help. I am trying to embed ansi sql in a c program on
>> SunOS 5.5.1 using proc 2.2.2. After precompiling, compiling, and
>> linking with no errors, the executable causes a "Segmentation Fault
>> (coredump)" message when the CONNECT statement is reached. The
>> database is up and running (Oracle 7.3.2). Even the sample programs,
>> created with proc.mk, cause the error (sample1.pc, etc.). I'm using
>> all default settings, and have tried other settings with no change.
>>
>> Any ideas? Environment variables missing? Path incorrect? I'm lost?
>>
>> TIA,
>> Steve D.
>
>I know there was a problem with the Oracle shared libraries on
>HP-UX 10.x that caused the exact same problem you are
>describing with Oracle 7.3. You might want to check to see
>if there is an equivalent patch for this on SunOs.
>
>Sorry don't know what the HP-UX patch number is off hand.
>
>John K.
>
>
Received on Sat Aug 09 1997 - 00:00:00 CEST

Original text of this message