Segmentation fault in nsgetcinfo in aix 64-bit c code


 
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
LSEEK64(3)						     Linux Programmer's Manual							LSEEK64(3)

NAME
lseek64 - reposition 64-bit read/write file offset SYNOPSIS
#define _LARGEFILE64_SOURCE /* See feature_test_macros(7) */ #include <sys/types.h> #include <unistd.h> off64_t lseek64(int fd, off64_t offset, int whence); DESCRIPTION
The lseek(2) family of functions reposition the offset of the open file associated with the file descriptor fd to offset bytes relative to the start, current position, or end of the file, when whence has the value SEEK_SET, SEEK_CUR, or SEEK_END, respectively. For more details, return value, and errors, see lseek(2). Four interfaces are available: lseek(2), lseek64(), llseek(2), and _llseek(2). lseek() Prototype: off_t lseek(int fd, off_t offset, int whence); lseek(2) uses the type off_t. This is a 32-bit signed type on 32-bit architectures, unless one compiles with #define _FILE_OFFSET_BITS 64 in which case it is a 64-bit signed type. lseek64() Prototype: off64_t lseek64(int fd, off64_t offset, int whence); The library routine lseek64() uses a 64-bit type even when off_t is a 32-bit type. Its prototype (and the type off64_t) is available only when one compiles with #define _LARGEFILE64_SOURCE The function lseek64() is available since glibc 2.1, and is defined to be an alias for llseek(). llseek() Prototype: loff_t llseek(int fd, loff_t offset, int whence); The type loff_t is a 64-bit signed type. The library routine llseek() is available in glibc and works without special defines. However, the glibc headers do not provide a prototype. Users should add the above prototype, or something equivalent, to their own source. When users complained about data loss caused by a miscompilation of e2fsck(8), glibc 2.1.3 added the link-time warning "the `llseek' function may be dangerous; use `lseek64' instead." This makes this function unusable if one desires a warning-free compilation. _llseek() On 32-bit architectures, this is the system call that is used to implement all of the above functions. The prototype is: int _llseek(int fd, off_t offset_hi, off_t offset_lo, loff_t *result, int whence); For more details, see llseek(2). 64-bit systems don't need an _llseek() system call. Instead, they have an lseek(2) system call that supports 64-bit file offsets. ATTRIBUTES
For an explanation of the terms used in this section, see attributes(7). +----------+---------------+---------+ |Interface | Attribute | Value | +----------+---------------+---------+ |lseek64() | Thread safety | MT-Safe | +----------+---------------+---------+ SEE ALSO
llseek(2), lseek(2) COLOPHON
This page is part of release 4.15 of the Linux man-pages project. A description of the project, information about reporting bugs, and the latest version of this page, can be found at https://www.kernel.org/doc/man-pages/. Linux 2017-09-15 LSEEK64(3)