You have corrupted the file_name pointer. (example) This means that the filename filename originally lived at address 0x006000, but your code changed it so filename now references 0x005ff80. Or some other invalid address, like NULL.
To diagnose:
put this in your code:
Code:
printf("file_name reference on line %d = %p\n", __LINE__, file_name);
just before EVERY line that has file_name in it.
This User Gave Thanks to jim mcnamara For This Post:
sometimes for this code i get a segmentation fault for codes llike this
:
int main{
int * a= 0;
int b;
a = (int*)malloc(sizeof(int));
///some code using these variable but no freeing of a
if(a){
free(a);
a = 0;
}
return... (3 Replies)
I have written a program which takes a directory as command line arguments and displays all the dir and files in it.
I don't know why I have a problem with the /etc directory.It displays all the directories and files untill it reaches a sub directory called peers which is in /etc/ppp/peers.the... (4 Replies)
Hi ,
During execution a backup binary i get following error
"Program error 11 (Segmentation fault), saving core file in '/usr/datatools"
Riyaz (2 Replies)
Hi,
I am having this segmentation fault not in the following program, bt. in my lab program . My lab program is horrible long so cannot post it here bt. I am using the following logic in my program which is giving the segmentation fault. Bt. if I run this sample program as it is it dosen't give... (3 Replies)
I'm getting a segmentation fault. I'm new to Linux programming. Thanks so much for all of your input.:eek:
#include </usr/include/mysql++/mysql++.h>
#include <stdio.h>
#include <iostream>
#include <sstream>
#include <string.h>
using namespace std;
int outputToImport(const char*... (1 Reply)
I use a binary name (ie polo) it gets some parameter , so for debugging normally i do this :
i wrote script for watchdog my app (polo) and check every second if it's not running then start it , the problem is , if my app , remain in state of segmentation fault for a while (ie 15 ... (6 Replies)
Hi Guys,
I just installed and booted a zone called testzone. When I logged in remotely and tried changing to root user I get this error:
"Segmentation fault"
Can someone please help me resolve this?
Thanks alot (2 Replies)
Hi everyone
Need to get version of npm application that have several output like this:
root: nmp -version
10
root: nmp -version
10
root: nmp-new -version
3.1
root: nmp-old -version
Segmentation fault
count them , after that write to the file like this:
10 2
3.1 1 (1 Reply)
Oddities with gcc, 2.95.3 for the AMIGA and 4.2.1 for MY current OSX 10.14.1...
I am creating a basic calculator for the AMIGA ADE *NIX emulator in C as it does not have one.
Below are two very condensed snippets of which I have added the results inside the each code section.
IMPORTANT!... (11 Replies)
Discussion started by: wisecracker
11 Replies
LEARN ABOUT OPENSOLARIS
halockrun
halockrun(1M) System Administration Commands halockrun(1M)NAME
halockrun - run a child program while holding a file lock
SYNOPSIS
/usr/cluster/bin/halockrun [-nsv] [-e exitcode] lockfilename
prog [args]
DESCRIPTION
The halockrun utility provides a convenient means to claim a file lock on a file and run a program while holding that lock. As this utility
supports script locking, this utility is useful when programming in scripting languages such as the Bourne shell. See sh(1).
halockrun opens the file lockfilename and claims an exclusive mode file lock on the entire file. See fcntl(2)fcntl(2)). Then it runs the
program prog with arguments args as a child process and waits for the child process to exit. When the child exits, halockrun releases the
lock, and exits with the same exit code with which the child exited.
The overall effect is that the child prog is run as a critical section, and that this critical section is well-formed, in that no matter
how the child terminates, the lock is released.
If the file lockfilename cannot be opened or created, then halockrun prints an error message on stderr and exits with exit code 99.
You can run this command in the global zone or in a non-global zone. The command affects only the global or non-global zone in which you
issue the command.
OPTIONS
The following options are supported:
-e exitcode Normally, errors detected by halockrun exit with exit code 99. The -e option provides a means to change this
special exit code to a different value.
-n The lock should be requested in non-blocking mode: if the lock cannot be granted immediately, halockrun exits
immediately, with exit code 1, without running prog. This behavior is not affected by the -e option.
Without the -n option, the lock is requested in blocking mode, thus, the halockrun utility blocks waiting for
the lock to become available.
-s Claim the file lock in shared mode, rather than in exclusive mode.
-v Verbose output, on stderr.
EXIT STATUS
Errors detected by halockrun itself, such that the child process was never started, cause halockrun to exit with exit code 99. (This exit
code value can be changed to a different value using the -e option. See OPTIONS.
Otherwise, halockrun exits with the same exit code with which the child exited.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWscu |
+-----------------------------+-----------------------------+
|Interface Stability |Evolving |
+-----------------------------+-----------------------------+
SEE ALSO fcntl(2), attributes(5)Sun Cluster 3.2 10 Apr 2006 halockrun(1M)