HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Problem in EXEC system call
Operating System - HP-UX
1832995
Members
2240
Online
110048
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-03-2001 08:23 PM
05-03-2001 08:23 PM
Problem in EXEC system call
Hi ,
I' ve encountered a strange problem while using the exec() system call.
The description of the problem is as follows:
We are using "execl()' system call to load program B in the process space to replace the current program A.
This call is executed successfully and the program B starts executing in the place of the program A.
Now at the end of the program B we again want to return back to program A and hence we again use execl() to load program A.
At this point of time "execl" system call fails and errno is set to "ENOMEM" i.e. Not Enough Memory.
The size of the program A is 425 KB and that of program B is 45 KB.
Is there any way to retain the process space even if the new program is less than size of the previous program ???
Another imp observation is that the same process of using execl goes successfully when we do execl between program A and program C.
The size of the program C is 216 KB.
Can you give me some pointers in this problem ???
Thanks
I' ve encountered a strange problem while using the exec() system call.
The description of the problem is as follows:
We are using "execl()' system call to load program B in the process space to replace the current program A.
This call is executed successfully and the program B starts executing in the place of the program A.
Now at the end of the program B we again want to return back to program A and hence we again use execl() to load program A.
At this point of time "execl" system call fails and errno is set to "ENOMEM" i.e. Not Enough Memory.
The size of the program A is 425 KB and that of program B is 45 KB.
Is there any way to retain the process space even if the new program is less than size of the previous program ???
Another imp observation is that the same process of using execl goes successfully when we do execl between program A and program C.
The size of the program C is 216 KB.
Can you give me some pointers in this problem ???
Thanks
It Has Been...
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-04-2001 02:03 AM
05-04-2001 02:03 AM
Re: Problem in EXEC system call
have u used free() at the end of program B
never give up
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-04-2001 09:59 AM
05-04-2001 09:59 AM
Re: Problem in EXEC system call
Never seen this one before and it's very strange. What OS and compiler are you using?
I think I would try the other variants of exec
(execle,execlp,etc.).
Another workaround might be to
Use system in Program A to call program B and then when you exit B; A is where you left it.
These sizes you are giving us - what are they?
If they are the size of the executable that means almost nothing other than a hint at the size of the text section. Use glance, top, or a ps -l to get a better idea of the total program size.
I think with a little more data we can pin this one down. After all, the shell and processes spawned under it has to do exactly what you are doing.
Just some food for thought, Clay
I think I would try the other variants of exec
(execle,execlp,etc.).
Another workaround might be to
Use system in Program A to call program B and then when you exit B; A is where you left it.
These sizes you are giving us - what are they?
If they are the size of the executable that means almost nothing other than a hint at the size of the text section. Use glance, top, or a ps -l to get a better idea of the total program size.
I think with a little more data we can pin this one down. After all, the shell and processes spawned under it has to do exactly what you are doing.
Just some food for thought, Clay
If it ain't broke, I can fix that.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP