Top Forums Programming Application crashes in FreeBSD 7.1 while working ok in FreeBSD 6.3 Post 302278433 by Seenquev on Tuesday 20th of January 2009 08:07:17 AM
Old 01-20-2009
Ok, the problem is solved. It was not FreeBSD's fault but mine - wrong use of delete operator caused these crashes. In FreeBSD 6.3 it was crashing only once per few hours, in FreeBSD 7.1 the crash was occuring after application start.

Thank you for your time anyway.

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

need help with FreeBSD!!!

Hi I want to write to my output_file using: if((fptr = creat(output_file, _S_IWRITE)) == -1) { printf("output_file..."..); return (1); } for(...) { _write(fptr, buffer, BUF_SIZE); } It says "_S_IWRITE" undeclared!!! Anybody knows what function I can use for that and what I... (3 Replies)
Discussion started by: lacasa
3 Replies

2. UNIX for Dummies Questions & Answers


I am on AOL now,and i am using 56 k,i was gonna install FreeBSD,but i dont know if aol works on BSD,or my modem. Do they work on BSD? (2 Replies)
Discussion started by: kita
2 Replies

3. UNIX for Dummies Questions & Answers

Freebsd 4.5

i am new at unix and am VERY confused about the compression processes. what progs do i need to unzip and zip files? there must be a standard one similar to winzip? (1 Reply)
Discussion started by: Mindscan
1 Replies

4. UNIX for Dummies Questions & Answers


What is FreeBSD, who does use Free? (3 Replies)
Discussion started by: cyberangel
3 Replies

5. BSD

I want the Best FREEBSD

B]I want the best of the best FreeBSD version for my study in Unix...please sugest me... Thanks (5 Replies)
Discussion started by: israel
5 Replies

6. UNIX for Dummies Questions & Answers

Freebsd and win 2000 working 2gether?

Hi Brothers, Please, I've just purchased a new PC and I would like to have both win 2000 and freebsd in the same hard drive, ( 40GB and 128Mb ) can you please help how to set up my new hard drive , please! Thank you..... aka Polymorphous (2 Replies)
Discussion started by: Polymorphous
2 Replies

7. BSD

please help me in FreeBSD

Hi to all, Iam doing a project in Free BSD and i am stuck with a puzzle. Please any one of you clarify my doubt : How to add a mechanism to check the status of the file system which alerts the root user via. email if any single partition is greater than 90% full. This alert should include the... (3 Replies)
Discussion started by: tadakamalla
3 Replies

8. Solaris

application Crashes on memset ?? any suggestions

Hi All, we have an application that is written in 'C' programming to connects to various servers in the organization. The bellow code establish a TCP connection to connect to the remote servers. the application works perfectly ok, but, after some time the entire process get's crashed and... (2 Replies)
Discussion started by: sudharma
2 Replies

9. Fedora


I'm using Windows mostly and the only *nix thing I used during my life was cygwin (I like command line :)). But currently I have (by an occasion) a DVD with latest FreeBSD. I don't know why, but I want to install it... But probably, this OS is too difficult for a beginner. I heard, it's used on... (3 Replies)
Discussion started by: TeenageWerewolf
3 Replies

10. UNIX for Advanced & Expert Users

motif application crashes while calling XtDestroyWidget

Hi All, We have a 32bit Motif Gui application. Now we ported the application from Solaris to Linux and the system is crashing very frequently. On our analysis we could find that this issue happened when we are closing the forms in our application. When the forms are closed we will delete the forms... (0 Replies)
Discussion started by: sanushchacko
0 Replies
CRASH(8)						    BSD System Manager's Manual 						  CRASH(8)

crash -- FreeBSD system failures DESCRIPTION
This section explains a bit about system crashes and (very briefly) how to analyze crash dumps. When the system crashes voluntarily it prints a message of the form panic: why i gave up the ghost on the console, and if dumps have been enabled (see dumpon(8)), takes a dump on a mass storage peripheral, and then invokes an automatic reboot procedure as described in reboot(8). Unless some unexpected inconsistency is encountered in the state of the file systems due to hardware or software failure, the system will then resume multi-user operations. The system has a large number of internal consistency checks; if one of these fails, then it will panic with a very short message indicating which one failed. In many instances, this will be the name of the routine which detected the error, or a two-word description of the incon- sistency. A full understanding of most panic messages requires perusal of the source code for the system. The most common cause of system failures is hardware failure, which can reflect itself in different ways. Here are the messages which are most likely, with some hints as to causes. Left unstated in all cases is the possibility that hardware or software error produced the mes- sage in some unexpected way. cannot mount root This panic message results from a failure to mount the root file system during the bootstrap process. Either the root file system has been corrupted, or the system is attempting to use the wrong device as root file system. Usually, an alternate copy of the system binary or an alternate root file system can be used to bring up the system to investigate. Most often this is done by the use of the boot floppy you used to install the system, and then using the ``fixit'' floppy. init: not found This is not a panic message, as reboots are likely to be futile. Late in the bootstrap procedure, the system was unable to locate and execute the initialization process, init(8). The root file system is incorrect or has been corrupted, or the mode or type of /sbin/init forbids execution or is totally missing. ffs_realloccg: bad optim ffs_valloc: dup alloc ffs_alloccgblk: cyl groups corrupted ffs_alloccg: map corrupted blkfree: freeing free block blkfree: freeing free frag ifree: freeing free inode These panic messages are among those that may be produced when file system inconsistencies are detected. The problem generally results from a failure to repair damaged file systems after a crash, hardware failures, or other condition that should not normally occur. A file system check will normally correct the problem. timeout table full This really should not be a panic, but until the data structure involved is made to be extensible, running out of entries causes a crash. If this happens, make the timeout table bigger. init died (signal #, exit #) The system initialization process has exited with the specified signal number and exit code. This is bad news, as no new users will then be able to log in. Rebooting is the only fix, so the system just does it right away. That completes the list of panic types you are likely to see. If the system has been configured to take crash dumps (see dumpon(8)), then when it crashes it will write (or at least attempt to write) an image of memory into the back end of the dump device, usually the same as the primary swap area. After the system is rebooted, the program savecore(8) runs and preserves a copy of this core image and the current system in a specified directory for later perusal. See savecore(8) for details. To analyze a dump you should begin by running kgdb(1) on the system load image and core dump. If the core image is the result of a panic, the panic message is printed. For more details consult the chapter on kernel debugging in the FreeBSD Developers' Handbook ( SEE ALSO
kgdb(1), dumpon(8), reboot(8), savecore(8) HISTORY
The crash manual page first appeared in FreeBSD 2.2. BSD
July 23, 2011 BSD

Featured Tech Videos

All times are GMT -4. The time now is 12:04 AM.
Unix & Linux Forums Content Copyright 1993-2021. All Rights Reserved.
Privacy Policy