Login or Register to Ask a Question and Join Our Community


AIX

Segmentation fault in nsgetcinfo in aix 64-bit c code

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Operating Systems AIX Segmentation fault in nsgetcinfo in aix 64-bit c code
# 1  
Old 05-27-2009
Segmentation fault in nsgetcinfo in aix 64-bit c code
Hello,

I am running on a AIX5.2 server with Oracle 10g and 9i. My code compiles and works fine in 32-bit mode. The

same code compiles in 64-bit and runs good. The program catches CNTRL-C signal to terminate. Only on 64-bit code

when i hit CNTRL-C, the program exits with segmentation fault on dbx debugger. The whole program runs in a while

loop infinitely untill a CNTRL-C is hitted. The program takes sql from oracle and sends to queue. It shows error if

bulk of SQLs are processed and after i hit CNTRL-C. The error is

Segmentation fault in nsgetcinfo at 0x900000002ccfd18 ($t1)
0x900000002ccfd18 (nsgetcinfo+0x38) e8dd02b0 ld r6,0x2b0(r29)

The error is same when i hit CNTRL-C when am at any point in the while loop. So i am not able to trace the issue.

Please help. Lots of malloc and realloc is used. Anything to change while porting from 32-bit to 64-bit?
Malloc format used is

Code:
char *str1 = NULL;
int intStartIndex = 10; /*returns from other function*/
str1 = (char*)malloc((intStartIndex+1) * sizeof(char));
strcpy(str1,"");
strcpy(str1,str2); /*str2 is a character pointer with length 10*/

Please help. I am fed up with this problem for last one week!!
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Programming

Why does this example C code run and yet SHOULD either not compile or give a segmentation fault?

Apologies for any typos... Well guys, been researching 'goto' in C and they say that you can't 'goto' labels in another function as a segmentation fault will occur. However I have found a way to 'goto' a label in another function that is NOT main() using the asm() function. As you know I... (14 Replies)
Discussion started by: wisecracker
14 Replies

2. Programming

C. To segmentation fault or not to segmentation fault, that is the question.

Oddities with gcc, 2.95.3 for the AMIGA and 4.2.1 for MY current OSX 10.14.1... I am creating a basic calculator for the AMIGA ADE *NIX emulator in C as it does not have one. Below are two very condensed snippets of which I have added the results inside the each code section. IMPORTANT!... (11 Replies)
Discussion started by: wisecracker
11 Replies

3. Programming

This code keeps giving me a segmentation fault why?

#include<stdlib.h> #include <pthread.h> #include "tlpi_hdr.h" #include <stdio.h> static volatile int glob = 0; static struct { pthread_t t1,t2; } *thread; static void * /* Loop 'arg' times incrementing 'glob' */ threadFunc(void *arg) { int loops = *((int *) arg); ... (1 Reply)
Discussion started by: fwrlfo
1 Replies

4. Programming

Using gdb, ignore beginning segmentation fault until reproduce environment segmentation fault

I use a binary name (ie polo) it gets some parameter , so for debugging normally i do this : i wrote script for watchdog my app (polo) and check every second if it's not running then start it , the problem is , if my app , remain in state of segmentation fault for a while (ie 15 ... (6 Replies)
Discussion started by: pooyair
6 Replies

5. UNIX for Advanced & Expert Users

segmentation fault with ps

What does this mean and why is this happening? $ ps -ef | grep ocular Segmentation fault (core dumped) $ ps -ef | grep ocular Segmentation fault (core dumped) $ ps aux | grep ocular Segmentation fault (core dumped) $ ps Segmentation fault (core dumped) $ pkill okular $ ps... (1 Reply)
Discussion started by: cokedude
1 Replies

6. Programming

C code : Segmentation fault

Hi Friends, I have written a small code in C which performs the below operations Task : 1 ) read line by line from a file. 2 ) assuming 3th and 4th fields of the file as GN and GNTO 3 ) The target file should contain all the fields except GNTO. 4... (3 Replies)
Discussion started by: kiran_bhatter
3 Replies

7. Programming

segmentation fault

If I do this. Assume struct life { char *nolife; } struct life **life; // malloc initialization & everything if(life->nolife == 0) Would I get error at life->nolife if it is equal to 0. wrong accession? (3 Replies)
Discussion started by: joey
3 Replies

8. Linux

Segmentation fault

Hi, on a linux Red HAT(with Oracle DB 9.2.0.7) I have following error : RMAN> delete obsolete; RMAN retention policy will be applied to the command RMAN retention policy is set to redundancy 2 using channel ORA_DISK_1 Segmentation fault What does it mean ? And the solution ? Many thanks. (0 Replies)
Discussion started by: big123456
0 Replies

9. AIX

Segmentation fault

Hi , During execution a backup binary i get following error "Program error 11 (Segmentation fault), saving core file in '/usr/datatools" Riyaz (2 Replies)
Discussion started by: rshaikh
2 Replies

10. Programming

segmentation fault

hi all i'm trying to execute a c program under linux RH and it gives me segmentation fault, this program was running under unix at&t anybody kow what the problem could be? thanx in advance regards (2 Replies)
Discussion started by: omran
2 Replies
Login or Register to Ask a Question

LEARN ABOUT X11R4

perlcc

PERLCC(1)						 Perl Programmers Reference Guide						 PERLCC(1)

NAME

       perlcc - generate executables from Perl programs

SYNOPSIS

	   $ perlcc hello	       # Compiles into executable 'a.out'
	   $ perlcc -o hello hello.pl  # Compiles into executable 'hello'

	   $ perlcc -O file	       # Compiles using the optimised C backend
	   $ perlcc -B file	       # Compiles using the bytecode backend

	   $ perlcc -c file	       # Creates a C file, 'file.c'
	   $ perlcc -S -o hello file   # Creates a C file, 'file.c',
				       # then compiles it to executable 'hello'
	   $ perlcc -c out.c file      # Creates a C file, 'out.c' from 'file'

	   $ perlcc -e 'print q//'     # Compiles a one-liner into 'a.out'
	   $ perlcc -c -e 'print q//'  # Creates a C file 'a.out.c'

	   $ perlcc -I /foo hello      # extra headers (notice the space after -I)
	   $ perlcc -L /foo hello      # extra libraries (notice the space after -L)

	   $ perlcc -r hello	       # compiles 'hello' into 'a.out', runs 'a.out'.
	   $ perlcc -r hello a b c     # compiles 'hello' into 'a.out', runs 'a.out'.
				       # with arguments 'a b c'

	   $ perlcc hello -log c       # compiles 'hello' into 'a.out' logs compile
				       # log into 'c'.

DESCRIPTION

       perlcc creates standalone executables from Perl programs, using the code generators provided by the B module. At present, you may either
       create executable Perl bytecode, using the "-B" option, or generate and compile C files using the standard and 'optimised' C backends.

       The code generated in this way is not guaranteed to work. The whole codegen suite ("perlcc" included) should be considered very experimen-
       tal. Use for production purposes is strongly discouraged.

OPTIONS

       -Llibrary directories
	   Adds the given directories to the library search path when C code is passed to your C compiler.

       -Iinclude directories
	   Adds the given directories to the include file search path when C code is passed to your C compiler; when using the Perl bytecode
	   option, adds the given directories to Perl's include path.

       -o output file name
	   Specifies the file name for the final compiled executable.

       -c C file name
	   Create C code only; do not compile to a standalone binary.

       -e perl code
	   Compile a one-liner, much the same as "perl -e '...'"

       -S  Do not delete generated C code after compilation.

       -B  Use the Perl bytecode code generator.

       -O  Use the 'optimised' C code generator. This is more experimental than everything else put together, and the code created is not guaran-
	   teed to compile in finite time and memory, or indeed, at all.

       -v  Increase verbosity of output; can be repeated for more verbose output.

       -r  Run the resulting compiled script after compiling it.

       -log
	   Log the output of compiling to a file rather than to stdout.

perl v5.8.9							    2009-04-13								 PERLCC(1)