Sponsored Content
Top Forums Programming open() system call in c++???? Post 302623293 by Corona688 on Friday 13th of April 2012 11:25:23 AM
Old 04-13-2012
In C, if you don't declare them, they may crash, so that's pretty "mandatory". But the compiler will only warn you.
 

9 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

how to differentiate system call from library call

Hi, Ho do I differentiate system call from library call? for example if I am using chmod , how do I find out if it is a system call or library call? Thanks Muru (2 Replies)
Discussion started by: muru
2 Replies

2. Programming

c system call

How the c compiler differentiates the system calls and function calls? (1 Reply)
Discussion started by: rangaswamy
1 Replies

3. Shell Programming and Scripting

system call

Hi, How to write a system calls in a script ? > cd $HOME > ls -ltr thanks in advance.. (10 Replies)
Discussion started by: hegdeshashi
10 Replies

4. Programming

C:system call

Hi I'm studing the system call. I've written a small program that return the time spent in doing some operations. Now I'd like to write one that return the time spent in user mode of a process. I'm reading that i should use the tms struct: clock_t times(struct tms *buf); struct tms {... (2 Replies)
Discussion started by: Dedalus
2 Replies

5. UNIX for Advanced & Expert Users

System Call Wrapper of 'open'

When the programmer use 'open' function, the process is like below. "open -> system call wrapper of open in Glibc -> syscall_open in kernel" I found the wrapper of open, but there is no implementation like 'int $80'. int __open (file, oflag) const char *file; int oflag; { ... (3 Replies)
Discussion started by: yuno96
3 Replies

6. Programming

Is there a system call other than 'open' for opening very large files?

Dear all, Inside a C program, I want to open a very big file (about 12 GB) in order to read its content. Here is the code: /* argv contains the path to the file. */ inputFileDescriptor = open(argv, O_RDONLY); if (inputFileDescriptor < 0) { ... (6 Replies)
Discussion started by: dariyoosh
6 Replies

7. Programming

system call

I have a cgi script which is called after certain time interval, which has this: system ("ls -l /tmp/cgic* | grep -v \"cgicsave.env\" | awk '{print $5}'"); During the execution of this script,the output is 0 sometimes. But due to this the system call is not working at all and doesnt o/p... (2 Replies)
Discussion started by: xs2punit
2 Replies

8. Programming

need help with system call

hi everyone i wrote a system call and compiled the kernel succesfully... my system call is in a file in the kernel folder named my_syscall1.c (kernel/my_syscall1.c) the header file for this system call i added it in the folder include like this include/my_syscall1/my_syscall1.h my problem is... (2 Replies)
Discussion started by: demis87
2 Replies

9. Shell Programming and Scripting

system call

Trying to figure out a load issue with a webserver. I have traced a php script and noticed the following connect(4, {sa_family=AF_INET, sin_port=htons(3306), sin_addr=inet_addr("XX.XX.XX.XX")}, 16) = -1 EINPROGRESS (Operation now in progress) <0.000035> poll(, 1, 2000) = 1 () <0.000120>... (5 Replies)
Discussion started by: rajan007
5 Replies
cr_read(3)						     Library Functions Manual							cr_read(3)

NAME
cr_read - read from crash dump SYNOPSIS
DESCRIPTION
The function attempts to read the memory area defined by mem_page and num_pages into the buffer pointed to by buf from the crash dump opened using crash_cb. The starts at the position in the crash dump associated with the physical memory offset given by mem_page. If the physical memory page mem_page does not exist in the crash dump, sets *num_pages to 0 and returns 0. No data transfer will occur past a page of memory that does not exist in the crash dump. If the starting position, mem_page, plus the read length, *num_pages, goes past an area of memory that does not exist in the crash dump, sets *num_pages to the number of consecutive pages (starting at mem_page) actually read. RETURN VALUE
Returns zero for success. Other possible return values are described in libcrash(5). EXAMPLES
Assuming a process opened a crash dump, the following call to cr_read(3) reads the first pages from the crash dump into the buffer pointed to by mybuf: WARNINGS
may return fewer pages than requested due to implementation details. Always check the number of pages returned. If they are fewer than requested, issue a new request starting at the first page not returned. Only if that new request reads zero pages (or returns an error) can you be sure that the page was not dumped. AUTHOR
was developed by HP. SEE ALSO
cr_open(3), libcrash(5). cr_read(3)
All times are GMT -4. The time now is 11:05 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy