Whether the following piece of code is placed in the read-only memory of code (text) segment or data segment?
I am getting two different answers while searching in google that's why the confusion is
Hi royalibrahim,
The declaration 'char *a = "hello"' is actually allocated in the .rodata (read-only data) and not in the .text section (in an ELF binary). I wrote a small code to verify
this.
I compiled it and dumped the .rodata section of the ELF using objdump.
How do I filter a long report, with the "STARTWORD" and "STOPWORD" as the variables to use in my awk command, to print the whole data segment that only contains the matched start/stop word?
awk '/start/, /stop/' file <- this prints the line, though I need to print the whole segment. Newline... (1 Reply)
Hi
1) Please go through the following code :
char string2;
char string1;
main()
{
memcpy(string2,"SENDER ",12);
strcpy(string1,"******");
printf("%s\n%s\n",string1,string2);
}
2) and the output of... (7 Replies)
When run it, segment fault.
What is wrong?
#include <stdio.h>
#include <stdlib.h>
const int max =20;
//****************************************************
// Input Matrix
//****************************************************
void inMatrixAA(int *AA, int row, int col)... (9 Replies)
Hi,
as per my Unix admin all parameters in Ulimit are set to Unlimited in Hard limits but some how few profiles setting data segment part to limited number value. So i wanted to over write in my profile to set unlimited as hard limits are set to unlimited. What is the command to set ulimit for... (1 Reply)
Hi guys,
Are all users authorised to modify the data segment and stack segment to unlimited on AIX?
Is a reboot required after giving ulimit -d unlimited?
Thanks
vandi (2 Replies)
Hi to all.
I'm reciving a "Segment violation" error from this code and I don't know why.
void insertAtEnd(NodeType *pList) {
char element;
printf("Introduce a element: \n");
setbuf(stdin, NULL);
scanf("%c", &element);
//Find the end of the list;
while... (4 Replies)
Hi guys,
I use AIX version 5 on IBM Power 5+ machine. I am currently trying to experiment with sort of self-modifying code, like this:
ucontext_t ut;
getcontext(&ut);
int iar = ut.uc_mcontext.jmp_context.iar;
int pageSize = getpagesize();
int rest = iar % pageSize;
void *ptr = iar -... (6 Replies)
I always get segment fault, why? can sb help me and modify it, I have spend on much time on
#include <pthread.h>
#include <stdio.h>
#include <stdlib.h>
#include <sys/time.h>
#include <string.h>
#define MAX 10
pthread_t thread;
void *thread1()
{
int *a;
int i, n;
... (1 Reply)
Discussion started by: yanglei_fage
1 Replies
LEARN ABOUT ULTRIX
shmat
shmop(2) System Calls Manual shmop(2)Name
shmop, shmat, shmdt - shared memory operations
Syntax
#include <sys/types.h>
#include <sys/ipc.h>
#include <sys/shm.h>
char *shmat (shmid, shmaddr, shmflg)
int shmid;
char *shmaddr;
int shmflg;
int shmdt (shmaddr)
char *shmaddr;
Description
The system call attaches the shared memory segment associated with the shared memory identifier specified by shmid to the data segment of
the calling process. The segment is attached at the address specified by one of the following criteria:
If shmaddr is equal to zero, the segment is attached at the first available address as selected by the system.
If shmaddr is not equal to zero and (shmflg & SHM_RND ) is true, the segment is attached at the address given by (shmaddr- (shmaddr modulus
SHMLBA )).
If shmaddr is not equal to zero and (shmflg & SHM_RND ) is false, the segment is attached at the address given by shmaddr.
The segment is attached for reading if (shmflg & SHM_RDONLY ) is true. Otherwise, it is attached for reading and writing.
The system call detaches from the calling process's data segment the shared memory segment located at the address specified by shmaddr.
Return Values
Upon successful completion, the return values are as follows:
o The system call returns the data segment start address of the attached shared memory segment.
o The system call returns a value of zero (0).
Otherwise, a value of -1 is returned, and errno is set to indicate the error.
Diagnostics
The system call fails and not attach the shared memory segment, if any of the following is true:
[EINVAL] The shmid is not a valid shared memory identifier.
[EACCES] Operation permission is denied to the calling process. For further information, see
[ENOMEM] The available data space is not large enough to accommodate the shared memory segment.
[EINVAL] The shmaddr is not equal to zero, and the value of (shmaddr- (shmaddr modulus SHMLBA )) is an illegal address.
[EINVAL] The shmaddr is not equal to zero, (shmflg & SHM_RND ) is false, and the value of shmaddr is an illegal address.
[EMFILE] The number of shared memory segments attached to the calling process would exceed the system imposed limit.
The fails and does not detach the shared memory segment if:
[EINVAL] The shmaddr is not the data segment start address of a shared memory segment.
See Alsoexecve(2), exit(2), fork(2), shmctl(2), shmget(2)shmop(2)