I am trying to illustrate the reverse order of parameters on the stack when passed to a function in C:
Result is:
This is as expected on the 64 bit system (Ubuntu 19.04)
When I pass a structure as a parameter the stack looks puzzling to me:
Now result is:
Parameter 3 is close to 1 and parameter 2 is not between 1 and 3? offsets look wrong to me.Please shed some light here, thanks in advance.
The compiler is gcc 7.4.0
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)
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)
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)
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)
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)
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
LEARN ABOUT NETBSD
dofileread
DOFILEREAD(9) BSD Kernel Developer's Manual DOFILEREAD(9)NAME
dofileread, dofilereadv, dofilewrite, dofilewritev -- high-level file operations
SYNOPSIS
#include <sys/file.h>
int
dofileread(struct lwp *l, int fd, struct file *fp, void *buf, size_t nbyte, off_t *offset, int flags, register_t *retval);
int
dofilewrite(struct lwp *l, int fd, struct file *fp, const void *buf, size_t nbyte, off_t *offset, int flags, register_t *retval);
int
dofilereadv(struct lwp *l, int fd, struct file *fp, const struct iovec *iovp, int iovcnt, off_t *offset, int flags, register_t *retval);
int
dofilewritev(struct lwp *l, int fd, struct file *fp, const struct iovec *iovp, int iovcnt, off_t *offset, int flags, register_t *retval);
DESCRIPTION
The functions implement the underlying functionality of the read(2), write(2), readv(2), and writev(2) system calls. They are also used
throughout the kernel as high-level access routines for file I/O.
The dofileread() function attempts to read nbytes of data from the object referenced by file entry fp into the buffer pointed to by buf. The
dofilewrite() function attempts to write nbytes of data to the object referenced by file entry fp from the buffer pointed to by buf.
The dofilereadv() and dofilewritev() functions perform the same operations, but scatter the data with the iovcnt buffers specified by the
members of the iov array.
The offset of the file operations is explicitly specified by *offset. The new file offset after the file operation is returned in *offset.
If the FOF_UPDATE_OFFSET flag is specified in the flags argument, the file offset in the file entry fp is updated to reflect the new file
offset, otherwise it remains unchanged after the operation.
The file descriptor fd is largely unused except for use by the ktrace framework for reporting to userlevel the process's file descriptor.
Upon successful completion the number of bytes which were transferred is returned in *retval.
RETURN VALUES
Upon successful completion zero is returned, otherwise an appropriate error is returned.
CODE REFERENCES
The framework for these file operations is implemented within the file sys/kern/sys_generic.c.
SEE ALSO file(9)BSD December 20, 2005 BSD