Sponsored Content
Top Forums Programming Problem shmat in HP-UX Titanium ia64. EINVAL Error Post 302340263 by dairby on Monday 3rd of August 2009 06:07:19 AM
Old 08-03-2009
Problem shmat in HP-UX Titanium ia64. EINVAL Error

I have a process that needs two active connections to the same zone of shared memory simultaneously.

The firs conection works ok, but when i do the second call to shmat it give me error 22 (EINVAL). Only works ok the second call to shmat if i disconnect the first connection (shmdt)

Steps: Iīm going to shared a integer.
1š.- Create shared memory OK:
iIdentificador = shmget(5000,sizeof(int),IPC_CREAT | 0777); //In the original source the key is not hardcode...

2š.-Connection 1 and view the integer shared. Works OK:
piIntegerShared_1=(int *)shmat(iIdentificador,NULL,0))
printf("\n\t =>Dato compartido [%ld]\n",*piIntegerShared_1);

3š.-Connection 2: ERROR !!!:
if((piIntegerShared_2=(int *)shmat(iIdentificador,NULL,0))==(void*)-1)
printf("\n\n\t ERROR shmat memoria2 [%d] [%s]",errno,strerror(errno));

Output: ERROR shmat memoria2 [22] [Invalid argument]

The connection 2 only works ok, if i before delete the connection 1 with:
shmdt(piIntegerShared_1);

Which is the problem in the step 3?
In Sun,AIX and Digital, i donīt have this problem all connection works ok. Only in HP-UX (Itanium - ia64) 11i Version 2: August 2003

Thanks,
David

Last edited by dairby; 08-03-2009 at 10:59 AM..
 

10 More Discussions You Might Find Interesting

1. HP-UX

shmat() permission denied, what's this?

I have installed an application that runs correctly for root but not other users. The application generates an error that indicates users don't have permission to attach to shared memory. A daemon process creates the shared memory segment. I've checked every permission I can think of but nothing... (2 Replies)
Discussion started by: km4hr
2 Replies

2. Programming

shmat problem

The first shmat in my program cannot fetch the start address of the shared memory. #include <stdio.h> #include <unistd.h> #include <sys/types.h> #include <sys/ipc.h> #include <sys/shm.h> int main(int argc,char *argv) { int pid; key_t mykey; int shmid; long *shm; long *shm2; ... (3 Replies)
Discussion started by: yong
3 Replies

3. UNIX for Dummies Questions & Answers

HP-UX 11.23 ia64 and Glance

I've been searching and cannot seem to find anywhere online a link to a manual for Glance. Does anyone have a link to this? I searched in here already and the links I found on a post from 2002 were dead. And more to the point, do you know if you can use Glance to see Disk I/O per logical... (2 Replies)
Discussion started by: LisaS
2 Replies

4. AIX

sharemem-f-shmat

Hi, I got this error from AIX 4.3.3/db2 7: * %SHAREMEM-F-SHMAT Error getting PUTPARM shared memory address , shmid=23029 * * 3630, errno=13 Anybody who know how to fix this? Thanks in advance, itik (1 Reply)
Discussion started by: itik
1 Replies

5. UNIX for Advanced & Expert Users

Problem shmat in HP-UX. EINVAL Error

I have a process that need two active connections to the same zone of shared memory. But when i do the second call to shmat it give me error 22 (EINVAL). Only works ok the second call to shmat if i disconnect the first connection (shmdt) In Sun,AIX and Digital, i donīt have this problem. ... (7 Replies)
Discussion started by: dairby
7 Replies

6. SuSE

problem of readdir on IA64 suse

Dear Experts, i am trying to find whether the given name is file or a directory dirp = opendir(dirname); direntp = readdir(dirp); if(direntp->d_type & DT_DIR) { printf("\n is a dirctory"); } else { //dir_or_file = Mtrue; printf("\n not a directory"); } it always... (9 Replies)
Discussion started by: vin_pll
9 Replies

7. Emergency UNIX and Linux Support

Gbrowse and GD installation in ia64 linux problem facing...

Hi all, I'm trying to install of Gbrowse recently. Unfortunately, I stuck at the step to install GD which are prerequisite for Gbrowse installation. I got try to install it, but it seems like got a lot of error message occurred :( And still can't fix the problem yet. I'm using ia64 linux... (10 Replies)
Discussion started by: patrick87
10 Replies

8. Programming

request_irq always returns EINVAL

request_irq always returns EINVAL What am I doing wrong here ? int mydrvr_open(struct inode *inode, struct file *filp) { int ret; printk("<1> \nModule Opened!"); //disable_irq(4); //free_irq(4, NULL); ret = request_irq(4, &imr_interrupt_handler,IRQF_SHARED,... (0 Replies)
Discussion started by: dragonpoint
0 Replies

9. Programming

shmat() with fixed address

Hi, I'm using Ubuntu 10.04 on a 64bit machine. In my shmat() call, I want to assign fixed memory address to shmaddr variable. I have no idea which address value to give. Some where in the net I read we can make use of sysproc info to know the user space addresses, but could not figure out how... (1 Reply)
Discussion started by: sajjar
1 Replies

10. Emergency UNIX and Linux Support

Redhat 4 and X-Fi Titanium not working

Hi, I have a dell T3500 running redhat 4 U8 with a X-Fi Titanium sound card. However alsaconf cant seem to see it. It shows up in lspci: uname -a Linux swlin114 2.6.9-89.0.23.ELsmp #1 SMP Fri Mar 5 23:27:13 EST 2010 x86_64 x86_64 x86_64 GNU/Linux 01:00.0 Audio device: Creative Labs... (2 Replies)
Discussion started by: chris.lewis28
2 Replies
SHMOP(2)						     Linux Programmer's Manual							  SHMOP(2)

NAME
shmop - shared memory operations SYNOPSIS
#include <sys/types.h> #include <sys/shm.h> void *shmat(int shmid, const void *shmaddr, int shmflg); int shmdt(const void *shmaddr); DESCRIPTION
The function shmat attaches the shared memory segment identified by shmid to the address space of the calling process. The attaching address is specified by shmaddr with one of the following criteria: If shmaddr is NULL, the system chooses a suitable (unused) address at which to attach the segment. If shmaddr isn't NULL and SHM_RND is asserted in shmflg, the attach occurs at the address equal to shmaddr rounded down to the nearest mul- tiple of SHMLBA. Otherwise shmaddr must be a page aligned address at which the attach occurs. If SHM_RDONLY is asserted in shmflg, the segment is attached for reading and the process must have read permission for the segment. Other- wise the segment is attached for read and write and the process must have read and write permission for the segment. There is no notion of a write-only shared memory segment. The brk value of the calling process is not altered by the attach. The segment will automatically be detached at process exit. The same segment may be attached as a read and as a read-write one, and more than once, in the process's address space. On a successful shmat call the system updates the members of the shmid_ds structure associated to the shared memory segment as follows: shm_atime is set to the current time. shm_lpid is set to the process-ID of the calling process. shm_nattch is incremented by one. Note that the attach succeeds also if the shared memory segment is marked to be deleted. The function shmdt detaches the shared memory segment located at the address specified by shmaddr from the address space of the calling process. The to-be-detached segment must be currently attached with shmaddr equal to the value returned by the its attaching shmat call. On a successful shmdt call the system updates the members of the shmid_ds structure associated with the shared memory segment as follows: shm_dtime is set to the current time. shm_lpid is set to the process-ID of the calling process. shm_nattch is decremented by one. If it becomes 0 and the segment is marked for deletion, the segment is deleted. The occupied region in the user space of the calling process is unmapped. SYSTEM CALLS
fork() After a fork() the child inherits the attached shared memory segments. exec() After an exec() all attached shared memory segments are detached from the process. exit() Upon exit() all attached shared memory segments are detached from the process. RETURN VALUE
On failure both functions return -1 with errno indicating the error. On success shmat returns the address of the attached shared memory segment, and shmdt returns 0. ERRORS
When shmat fails, errno is set to one of the following: EACCES The calling process has no access permissions for the requested attach type. EINVAL Invalid shmid value, unaligned (i.e., not page-aligned and SHM_RND was not specified) or invalid shmaddr value, or failing attach at brk. ENOMEM Could not allocate memory for the descriptor or for the page tables. The function shmdt can fail only if there is no shared memory segment attached at shmaddr, in such a case at return errno will be set to EINVAL. NOTES
Using shmat with shmaddr equal to NULL is the preferred, portable way of attaching a shared memory segment. Be aware that the shared mem- ory segment attached in this way may be attached at different addresses in different processes. Therefore, any pointers maintained within the shared memory must be made relative (typically to the starting address of the segment), rather than absolute. The following system parameter affects a shmat system call: SHMLBA Segment low boundary address multiple. Must be page aligned. For the current implementation the SHMBLA value is PAGE_SIZE. The implementation has no intrinsic limit to the per-process maximum number of shared memory segments (SHMSEG). CONFORMING TO
SVr4, SVID. SVr4 documents an additional error condition EMFILE. In SVID-v4 the type of the shmaddr argument was changed from char * into const void *, and the returned type of shmat() from char * into void *. (Linux libc4 and libc5 have the char * prototypes; glibc2 has void *.) SEE ALSO
ipc(5), shmctl(2), shmget(2) Linux 2.5 2002-01-05 SHMOP(2)
All times are GMT -4. The time now is 02:21 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy