Operating System - HP-UX
1833723 Members
3758 Online
110063 Solutions
New Discussion

Re: Pro*C, gcc, HPUX 11.0(64 bit),acc

 
Gibran
Occasional Contributor

Pro*C, gcc, HPUX 11.0(64 bit),acc

Hi,

Is acc support by Pro*C?

I am running a C/Pro*C program compiled using gcc (v. 2.95.2) on HPUX 11.0(64 bit L class with 4 CPU's and 4GB memory, 1 GB per CPU). I am using Oracle 8.1.6 32 bit. My OS was at an old patch level (May 2000) and my process WAS running perfectly. I've recently upgraded my patch level to Mar 2001 and am now getting periodic core dumps by my process with ORA-no data found errors in core file.

Second, the size of my executable on the OLD patch level is 1090608. The size now created (same exact source code) is 1053744.

When my process is running, it utilizes 99-100% CPU utilization.

Could there be an issue with the compilers?

Any ideas on why core dump? Please let me know if you need more info...



Life is work, Work is not life...
4 REPLIES 4
A. Clay Stephenson
Acclaimed Contributor

Re: Pro*C, gcc, HPUX 11.0(64 bit),acc

Hi,

My best suggestion is to compile everything with the -g or -g0 option to enable debugging
with gdb. A stack trace should pinpoint the problem.

Good Hunting, Clay
If it ain't broke, I can fix that.
Gibran
Occasional Contributor

Re: Pro*C, gcc, HPUX 11.0(64 bit),acc

We are already running gcc in debug mode. The code compiles flawlessly. I am getting core dump seemingly at random. Could there be an issue with the patch level??

Is aCC supported by Pro*C...It did not used to be (1999).

When would the OS deactivate
Life is work, Work is not life...
A. Clay Stephenson
Acclaimed Contributor

Re: Pro*C, gcc, HPUX 11.0(64 bit),acc

Hi,

I'm using Pro*C with aCC under both 11.0 and 11i without problem although my Oracle is 64-bit. But still, you should be able to now use gbd and one of your core files and zero in on this puppy. A stack trace on your core file should nail it.

Clay
If it ain't broke, I can fix that.
Gibran
Occasional Contributor

Re: Pro*C, gcc, HPUX 11.0(64 bit),acc

My stack trace is:

#0 0xc0180730 in ?? ()
Error accessing memory address 0x0: Invalid argument.

What types of cases would this occur??

Thanks in advance...
Life is work, Work is not life...