Sponsored Content
Top Forums UNIX for Dummies Questions & Answers Compiling with debugger flag -g fixes SEGfault (fortran90) Post 302481528 by drbones on Friday 17th of December 2010 08:03:21 PM
Old 12-17-2010
Thanks for quick and useful reply!!

I actually just figured out the issue by rigorously debugging with print* commands.

I was searching for x within a list x1, x2, x3...xn, but did not account for x<x1. D'oh! So despite executing without an issue, the result would have been garbage. I think you hit the nail on the head, I had no idea this could happen!
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

[Linux] How Do I Run Until Segfault

Hello, sorry if this has been posted before but i was wondering if there is a way to run a program until a segmentation fault is found. Currently i'm using a simple shell script which runs my program 100 times, sleeps 1 second because srand(time(0)) is dependent on seconds. Is there a possible... (1 Reply)
Discussion started by: aslambilal
1 Replies

2. Programming

how to avoid the segfault from Address 0x1cd00000103 out of bounds

After allocating memory for some variables, segfault is often to happen, due to the same reason: Address 0x1cd00000103 out of bounds It is welcome to recommend some treatments. Thanks e.g. is_done = 0x1cd00000103 <Address 0x1cd00000103 out of bounds>, hood = 0x23c00000247, c =... (11 Replies)
Discussion started by: cdbug
11 Replies

3. Solaris

Working around netscape 4.9 segfault on Solaris 8

We have a Solaris 8 server which users login to via VNC to get a desktop. On that desktop these users use Netscape Communicator 4.9 to access a very important mail account. Unfortunately Netscape has started segfaulting regularly. Does anyone have any ideas how I can try to find out what point... (1 Reply)
Discussion started by: aussieos
1 Replies

4. Programming

2 Problems: Segfault on ctrl+c and syslog() prob

1. Even if i have the handles for ctrl+c it gives off a segfault 2. syslog doesn't log LOG_ERR event with log masked specified or non specified, it logs LOG_WARNING however... #include <sys/types.h> /* include this before any other sys headers */ #include <sys/stat.h> #include <fcntl.h>... (2 Replies)
Discussion started by: james2432
2 Replies

5. Programming

id3lib SEGFAULT

Hello everyone, I'm writing a program using the id3lib unfortunately I've encountered with memory issue that cause segmentation fault. I tried to rerun and analyze the program with valgrind but it doesn't point me anywhere. I really stuck on this one. Valgrind output: ==14716== Invalid read of... (2 Replies)
Discussion started by: errb
2 Replies

6. Programming

Is Drive Valid Segfault

I have a program that allows users to specify the debug log file location and name. I have tried using the access() and stat() but they both segfault if the drive say (d:\) is invalid. Both seem to be fine if the drive exists. Could someone please point me in the direction to a function that... (1 Reply)
Discussion started by: robfwauk
1 Replies

7. Programming

Alternative debugger to GNU insight debugger

GNU insight debugger is not available now a days and it is required to debug/inspect assembly code as written in the book Assembly Language Programming step by step in Linux so my question is; is there any alternative to insight that I can use instead of insight in which I can get the same... (5 Replies)
Discussion started by: vectrum
5 Replies

8. Programming

segfault in pointer to string program

hello all, my question is not about How code can be rewritten, i just wanna know even though i am not using read only memory of C (i have declared str) why this function gives me segfault :wall:and the other code executes comfortably though both code uses same pointer arithmetic. ... (4 Replies)
Discussion started by: zius_oram
4 Replies

9. Programming

String array iteration causing segfault

I am populating an array of string and print it. But it going in infinite loop and causing segfault. char Name = { "yahoo", "rediff", "facebook", NULL }; main(int argc, char* argv) { int j = 0; ... (7 Replies)
Discussion started by: rupeshkp728
7 Replies

10. Programming

Segfault When Parsing Delimiters In C

Another project, another bump in the road and another chance to learn. I've been trying to open gzipped files and parse data from them and hit a snag. I have data in gzips with a place followed by an ip or ip range sort of like this: Some place:x.x.x.x-x.x.x.x I was able to modify some code... (6 Replies)
Discussion started by: Azrael
6 Replies
SA(8)							    BSD System Manager's Manual 						     SA(8)

NAME
sa -- print system accounting statistics SYNOPSIS
sa [-abcdDfijkKlmnqrstu] [-v cutoff] [file ...] DESCRIPTION
The sa utility reports on, cleans up, and generally maintains system accounting files. sa is able to condense the information in /var/account/acct into the summary files /var/account/savacct and /var/account/usracct, which con- tain system statistics according to command name and login id, respectively. This condensation is desirable because on a large system, /var/account/acct can grow by hundreds of blocks per day. The summary files are normally read before the accounting file, so that reports include all available information. If file names are supplied, they are read instead of /var/account/acct. After each file is read, if the summary files are being updated, an updated summary will be saved to disk. Only one report is printed, after the last file is processed. The labels used in the output indicate the following, except where otherwise specified by individual options: avio Average number of I/O operations per execution cp Sum of user and system time, in minutes cpu Same as cp k CPU-time averaged core usage, in 1k units k*sec CPU storage integral, in 1k-core seconds re Real time, in minutes s System time, in minutes tio Total number of I/O operations u User time, in minutes The options to sa are: -a List all command names, including those containing unprintable characters and those used only once. By default, sa places all names containing unprintable characters and those used only once under the name ``***other''. -b If printing command statistics, sort output by the sum of user and system time divided by number of calls. -c In addition to the number of calls and the user, system and real times for each command, print their percentage of the total over all commands. -d If printing command statistics, sort by the average number of disk I/O operations. If printing user statistics, print the average number of disk I/O operations per user. -D If printing command statistics, sort and print by the total number of disk I/O operations. -f Force no interactive threshold comparison with the -v option. -i Do not read in the summary files. -j Instead of the total minutes per category, give seconds per call. -k If printing command statistics, sort by the CPU-time average memory usage. If printing user statistics, print the CPU-time average memory usage. -K If printing command statistics, print and sort by the CPU-storage integral. -l Separate system and user time; normally they are combined. -m Print per-user statistics rather than per-command statistics. -n Sort by number of calls. -q Create no output other than error messages. -r Reverse order of sort. -s Truncate the accounting files when done and merge their data into the summary files. -t For each command, report the ratio of real time to the sum of user and system CPU times. If the CPU time is too small to report, ``*ignore*'' appears in this field. -u Superseding all other flags, for each entry in the accounting file, print the user ID, total seconds of CPU usage, total memory usage, number of I/O operations performed, and command name. -v cutoff For each command used cutoff times or fewer, print the command name and await a reply from the terminal. If the reply begins with ``y'', add the command to the category ``**junk**''. This flag is used to strip garbage from the report. By default, per-command statistics will be printed. The number of calls, the total elapsed time in minutes, total CPU and user time in min- utes, average number of I/O operations, and CPU-time averaged core usage will be printed. If the -m option is specified, per-user statistics will be printed, including the user name, the number of commands invoked, total CPU time used (in minutes), total number of I/O operations, and CPU storage integral for each user. If the -u option is specified, the uid, user and system time (in seconds), CPU storage integral, I/O usage, and command name will be printed for each entry in the accounting data file. If the -u flag is specified, all flags other than -q are ignored. If the -m flag is specified, only the -b, -d, -i, -k, -q, and -s flags are honored. The sa utility exits 0 on success, and >0 if an error occurs. FILES
/var/account/acct raw accounting data file /var/account/savacct per-command accounting summary database /var/account/usracct per-user accounting summary database SEE ALSO
lastcomm(1), acct(5), ac(8), accton(8) HISTORY
sa was written for NetBSD 1.0 from the specification provided by various systems' manual pages. Its date of origin is unknown to the author. AUTHORS
Chris G. Demetriou <cgd@postgres.berkeley.edu>. BUGS
The number of options to this program is absurd, especially considering that there's not much logic behind their lettering. The field labels should be more consistent. NetBSD's VM system does not record the CPU storage integral. CAVEATS
While the behavior of the options in this version of sa was modeled after the original version, there are some intentional differences and undoubtedly some unintentional ones as well. In particular, the -q option has been added, and the -m option now understands more options than it used to. The formats of the summary files created by this version of sa are very different than the those used by the original version. This is not considered a problem, however, because the accounting record format has changed as well (since user ids are now 32 bits). BSD
February 25, 1994 BSD
All times are GMT -4. The time now is 10:20 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy