Sponsored Content
Top Forums Programming Parameters placement on stack in C Post 303036086 by Don Cragun on Thursday 13th of June 2019 09:28:00 PM
Old 06-13-2019
The standards don't specify how parameters are placed on the stack when a function is invoked and any code that assumes that parameters are placed on the stack in the order given (or in the reverse of the order given) in the function declaration is highly likely to fail on some operating systems on some hardware.

When an operating system is ported to or designed from scratch, the compiler group, the link editor group, and the operating system group will study the hardware design documents and agree on a scheme that they believe will be fast and conserve space on that hardware for the operating system being designed. Note that the scheme may well have exceptions that apply alternative behaviors when a function is invoked that takes a variable number of parameters (e.g., printf()). The only portable way to write functions like printf() is to use the macros defined in the Standard C header <stdarg.h> (i.e., va_start, va_arg, va_copy, and va_end).
These 3 Users Gave Thanks to Don Cragun For This Post:
 

8 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

code placement

I'm sorry if something like this has already been posted, but I didn't find anything like it. I'm using ksh The code that I've come up with will initially print what I want, but will then keep repeating the second number. I'm just trying to teach myself and can't seem to find the code to work.... (16 Replies)
Discussion started by: scott78
16 Replies

2. AIX

Aixterm icon placement?

Hi, I'm using xterm and aixterm with Mwm on AIX, and having trouble controlling icon placement when minimising windows. Basically when I run an xterm or aixterm I want to be able to specify where the icon will be if minimised. The man page mentions the "#geometry Geometry" option to aixterm,... (1 Reply)
Discussion started by: cunningdavid
1 Replies

3. UNIX Desktop Questions & Answers

Controlling icon placement?

Hi, I'm using xterm and aixterm with Mwm on AIX, and having trouble controlling icon placement when minimising windows. Basically when I run an xterm or aixterm I want to be able to specify where the icon will be if minimised. The man page mentions the "#geometry Geometry" option to aixterm,... (1 Reply)
Discussion started by: cunningdavid
1 Replies

4. Programming

what is stack winding and stack unwinding

helo can u tell me what do you mean by stack winding and stack unwinding Regards, Amit (2 Replies)
Discussion started by: amitpansuria
2 Replies

5. Solaris

Data placement in SVM

Is it possible to place the data in inner or outer edge with SVM ( solaris volume manager ) or VxVM like we can do in AIX LVM ? (1 Reply)
Discussion started by: fugitive
1 Replies

6. UNIX for Dummies Questions & Answers

Kernel Stack vs User Mode Stack

Hi, I am new to the linux kernel development area. I want to know what is the difference between kernel mode stack and user mode stack? Does each process has a user mode stack and a kernel mode stack?? Or Each process has a user mode stack and there is only one kernel mode stack that is shared by... (4 Replies)
Discussion started by: saurabhkoar
4 Replies

7. Cybersecurity

Snort/NTOP Placement

I have been asked to place 2 (1 NTOP & 1 SNORT) boxes within our network as part of our tool kit for network monitoring and Intrusion detection. Out network is very simplistic and it layed out like this: internet | | Cisco 1811 Router (8x Layer 2 switch ports) ... (0 Replies)
Discussion started by: metallica1973
0 Replies

8. UNIX for Advanced & Expert Users

Unix linked-list placement

Hi, I am programming in kernel, and I want to use a double linked list that holds infos that every process could access and modify THIS list. So, I suppose it is a 'global' variable since every process(thread) can reach it, I am wondering where to put it? by changing some of the kernel files? (1 Reply)
Discussion started by: louisTan
1 Replies
varargs(3)						     Library Functions Manual							varargs(3)

NAME
varargs, va_arg, va_start, va_end - Handles a variable-length parameter list LIBRARY
Standard C Library (libc.a) SYNOPSIS
#include <varargs.h> va_alist va_dcl void va_start ( va_alist argp ); type va_arg ( va_alist argp, type ); void va_end ( va_alist argp ); PARAMETERS
argp Specifies a variable that the varargs macros use to keep track of the current location in the parameter list. Do not modify this variable. type Specifies the type to which the expected argument will be converted when passed as an argument. Unsigned char or short arguments are converted to unsigned int, and float arguments are converted to double. Different types can be mixed, but it is up to the rou- tine to know what type of argument is expected because the type cannot be determined at run time. DESCRIPTION
NOTE: When writing new code, it is recommended that you use stdarg instead of varargs. They both perform the same function, but stdarg is standards-compliant and varargs complies only with BSD conventions. The varargs set of macros allows you to write portable functions that accept a variable number of parameters. Subroutines that have vari- able-length parameter lists (such as the printf() function), but that do not use the varargs macros, are inherently nonportable because different systems use different parameter-passing conventions. The varargs macros are as follows: va_alist() Defines the type of the variable used to traverse the list. va_start() Initializes argp to point to the beginning of the list. The va_start() macro will be invoked before any access to the unnamed argu- ments. va_arg() Returns the next parameter in the list pointed to by argp. va_end() Cleans up at the end. Your function can traverse, or scan, the parameter list more than once. Start each traversal with a call to va_start() and end it with va_end(). EXAMPLE
The following example is a possible implementation of the execl() function: #include <varargs.h> #define MAXargS 100 /* ** execl is called by ** execl(file, arg1, arg2, . . . , (char *) 0); */ execl(va_alist) va_dcl { va_list ap; char *file; char *args[MAXargS]; int argno = 0; va_start(ap); file = va_arg(ap, char *); while ((args[argno++] = va_arg(ap, char *)) != (char *) 0) ; /* Empty loop body */ va_end(ap); return (execv(file, args)); } NOTES
The calling routine is responsible for specifying the number of parameters because it is not always possible to determine this from the stack frame. For example, the execl() function is passed a null pointer to signal the end of the list. The printf() function determines the number of parameters from its fmt parameter. AES Support Level: Temporary use RELATED INFORMATION
Functions: exec(2), printf(3), stdarg(3), vprintf(3) delim off varargs(3)
All times are GMT -4. The time now is 08:54 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy