Board index Oracle

Pro*c program failing with Segmentation fault (core dump) on AIX 4.3, Oracle 8.1.5 , Pro*c 8.1.5

Pro*c program failing with Segmentation fault (core dump) on AIX 4.3, Oracle 8.1.5 , Pro*c 8.1.5

Post by Chakravart » Sun, 28 Oct 2001 09:40:29



Pro*c Program failing with Segmentation Fault and core dumps almost
all times. No errors in compilation. Platform is 8.1.5 on AIX RS6000
4.3. Is this due to any bug or any OS problem. NO Oracle errors,
ORA-600 errors, NO trace files in the bdump ,or udump destination.
This pro*c code calls stored procedures with IN / OUT parameteres.
The stored procedures are functioning without any errors when executed
in SQL*PLUS Any suggestion to resolve the problem would be greatly
appreciated.

Thanks,
Chakravarthy.

 
 
 
Top

Pro*c program failing with Segmentation fault (core dump) on AIX 4.3, Oracle 8.1.5 , Pro*c 8.1.5

Post by Kenneth C Stah » Sun, 28 Oct 2001 11:26:10



> Pro*c Program failing with Segmentation Fault and core dumps almost
> all times. No errors in compilation. Platform is 8.1.5 on AIX RS6000
> 4.3. Is this due to any bug or any OS problem. NO Oracle errors,
> ORA-600 errors, NO trace files in the bdump ,or udump destination.
> This pro*c code calls stored procedures with IN / OUT parameteres.
> The stored procedures are functioning without any errors when executed
> in SQL*PLUS Any suggestion to resolve the problem would be greatly
> appreciated.

> Thanks,
> Chakravarthy.

The reason for segmentation faults is that you are attempting to access
an address location outside of your TEXT space. Almost invariably it
indicates either a bad pointer or that you have overflowed the
boundaries of the space to which a valid pointer points.

I could probably fix this for you. My rate is $150/hour and I require
root privileges to the server.

 
 
 
Top

1. Segmentation fault/Core Dump

We are migrating from Oracle 6 on a Pyramid MIS/12 to Oracle 7 on DEC Alpha
2100 under OSF/1 v3.0. One of our applications consists of Forms 3.0,
Menu 5.0, PL/SQL 1.0, Reportwriter 1.1, and SQL*Plus 3.0 scripts.
We have regenerated the <form>.inp and <menu>.sql files. The <menu>.dmm
and <report>.rep files can be executed and exited from without any errors.
However, when we exit the application (a "exit_form(NO_VALIDATE);" procedure),
we get a segmentation fault and a core file is created.

Here are the memory-related variables from our kernel config file;

semmni 100
semmns 550
semmsl 25
shmmax 4194304
shmseg 25

Any ideas as to why we are getting these core dumps?

Thanks in advance,
Brenda King-Wade

2. newbie question about deleting folders

3. Segmentation faults in PRO*C programs: HELP ??

4. Newsletter

5. Pro*C / Aix / Core Dump pb. resolved !

6. MIDIMAX

7. Upgrade and then PRO*C segmentation fault

8. ANN: JS Landscape 2.0 (Beta) Available

9. Pro*C Segmentation Fault on Solaris

10. pro*C segmentation fault!!!!!!!!

11. Solaris 8/Oracle 8 C++ program segmentation fault on connect

12. Segmentation Problem, Core dumped


All times are UTC
Board index