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
Most likely the text segment but some compilers can be forced to put it in the data segment using comand line switches...and if you really care print out its location using a debugger to find out whether it lies in the text or data segment...difference is that the text segment literal cant be modified but the data segment one can be.
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 HPUX
plock
plock(2) System Calls Manual plock(2)NAME
plock() - lock process, text, data, stack, or shared library in memory
SYNOPSIS DESCRIPTION
The system call allows the calling process to lock the text segment of the process (text lock), its data segment (data lock), or both its
text and data segment (process lock) into memory. Stack segments are also locked when data segments are locked. Shared library text and
shared library data segments (shlib lock) can also be locked. Locked segments are immune to all routine swapping. also allows these seg-
ments to be unlocked.
The effective user ID of the calling process must be a user with the privilege.
op must be one of the following:
Lock text and data segments into memory (process lock)
Lock text segment into memory (text lock)
Lock data segment into memory (data lock)
Remove locks
Lock shared library text and shared library data segments (shared library lock)
Lock text, data and shared library text and shared library data segments
into memory (process and shared library lock)
Lock text, shared library text and shared library data segments into memory
(text and shared library lock)
Lock data, shared library text and shared library data segments into memory
(data and shared library lock)
Although and the family of functions may be used together in an application, each may affect the other in unexpected ways. This
practice is not recommended.
Security Restrictions
Some or all of the actions associated with this system call require the privilege. Processes owned by the superuser have this privilege.
Processes owned by other users may have this privilege, depending on system configuration. See privileges(5) for more information about
privileged access on systems that support fine-grained privileges.
RETURN VALUE
returns the following values:
Successful completion.
Failure.
The requested operation is not performed. is set to indicate the error.
ERRORS
If fails, is set to one of the following values.
op is equal to and a process lock, a text lock, or a data lock already exists on the calling process.
op is equal to and a text lock or process lock already exists on the calling process.
op is equal to and a data lock, or process lock already exists on the calling process.
op is equal to and no type of lock exists on the calling process.
op is equal to and there are no unlocked shared library segments in the calling process.
op is equal to and a process lock, a text lock, or a data lock already exists on the calling process.
op is equal to and a text lock or process lock already exists on the calling process.
op is equal to and a data lock, or process lock already exists on the calling process.
op is not equal to one of the values specified in
is not allowed in a
window. See vfork(2).
There is not enough lockable memory in the system
to satisfy the locking request.
The effective user ID of the calling process
is not a user with the privilege.
EXAMPLES
The following call to locks the calling process in memory:
SEE ALSO setprivgrp(1M), exec(2), exit(2), fork(2), getprivgrp(2), mlock(2), vfork(2), privileges(5).
STANDARDS CONFORMANCE plock(2)