07-06-2011
What do you mean by "crashes your system"? How are you using it?
7z crashing your system, if you mean a catastrophic failure of some sort, is very unusual and may point to memory errors or some other hardware problem. I remember you complaining about random utilities segfaulting before, did you get that resolved?
10 More Discussions You Might Find Interesting
1. Linux
Hello all,
I'm trying to use gethostbyname_r function with 6 arguments in one of my functions. But the call to this crashes the program. Kindly help me in resolving this...
Compiler Info:
Linux target: i686-hardhat-linux
version: 3.3.1
The following is the piece of code I'm trying to... (1 Reply)
Discussion started by: rajans
1 Replies
2. Programming
Hi,
Could anyone tell me the reason why the following program crashes?
class A {
int x;
public:
A() {
cout << "from A()" << endl;
}
~A() {
cout << "from ~A()" << endl;
}
};
class B : public A {
public:
B() {
cout << "from B()"... (2 Replies)
Discussion started by: royalibrahim
2 Replies
3. UNIX Desktop Questions & Answers
Hello
The KDE konsole crashed after I changed the font size to 64. And It crashes every time when started. How can I get it back?
Thanks.
---------- Post updated at 08:23 AM ---------- Previous update was at 07:48 AM ----------
solved, I finally find the config file called consolerc. (0 Replies)
Discussion started by: vic005
0 Replies
4. SuSE
I am running openSUSE 11.2 with KDE4.5 on my eMachines e525. I just did a "zypper up" on my system and it reported that Chromium was going to be updated. I agreed and the when the update was finished I shut down Chromium and started it again. It flickered on the screen for a moment and crashed.... (6 Replies)
Discussion started by: Druonysus
6 Replies
5. Solaris
Production server crashes when there is no traffic on it. Can only recover by going to ALOM and reboot the server. This seems to happen about the same time every month. The only good thing is the server is not in production at the time of the crash.
I have been unable to locate any information in... (5 Replies)
Discussion started by: Joeentech
5 Replies
6. Fedora
We've been having issues for about a year, although thankfully they are in-frequent and randam. Meaning it happened a couple of times within a 3 month period, then stopped for a couple of months and then started again. It has happened twice now in the last month. At the stroke of midnight, ... (5 Replies)
Discussion started by: graybeard
5 Replies
7. Programming
Hi,
Can anyone tell me why the below program is crashing? and where exactly it is crashing. What is the corrective measure to be taken to make it work fine?
#include <iostream>
#include <cstring>
using namespace std;
class CString {
char* m_data;
public:
CString() :... (6 Replies)
Discussion started by: royalibrahim
6 Replies
8. Shell Programming and Scripting
I am running a perl/tk function that suddenly crashes in MainLoop. The gui just disappears and an X error is
thrown when the code tries to update the non-existent GUI. Any suggestions to debug the root cause which
destroys the mw gui?
-D- <block name> : <block_name> - 1
-D- row_column_id... (0 Replies)
Discussion started by: bob.pepple
0 Replies
9. UNIX and Linux Applications
I am trying to run apcupsd, but it will not retain contact the UPS
root@meow:/home/ethan/UPS/gapcmon-0.8.9# /etc/init.d/apcupsd start
Starting UPS power management:
A copy of the daemon is still running. If you just stopped it,
please wait about 5 seconds for it to shut down.... (0 Replies)
Discussion started by: Meow613
0 Replies
10. Web Development
The Apache server suddenly stops. I am running Debian Jessie
Here are some diagnostics:
root@meow:/var/www# apachectl configtest
AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1. Set the 'ServerName' directive globally to suppress... (4 Replies)
Discussion started by: Meow613
4 Replies
LEARN ABOUT DEBIAN
explain_kill_or_die
explain_kill_or_die(3) Library Functions Manual explain_kill_or_die(3)
NAME
explain_kill_or_die - send signal to a process and report errors
SYNOPSIS
#include <libexplain/kill.h>
void explain_kill_or_die(pid_t pid, int sig);
int explain_kill_on_error(pid_t pid, int sig);
DESCRIPTION
The explain_kill_or_die function is used to call the kill(2) system call. On failure an explanation will be printed to stderr, obtained
from the explain_kill(3) function, and then the process terminates by calling exit(EXIT_FAILURE).
The explain_kill_on_error function is used to call the kill(2) system call. On failure an explanation will be printed to stderr, obtained
from the explain_kill(3) function, but still returns to the caller.
pid The pid, exactly as to be passed to the kill(2) system call.
sig The sig, exactly as to be passed to the kill(2) system call.
RETURN VALUE
The explain_kill_or_die function only returns on success, see kill(2) for more information. On failure, prints an explanation and exits, it
does not return.
The explain_kill_on_error function always returns the value return by the wrapped kill(2) system call.
EXAMPLE
The explain_kill_or_die function is intended to be used in a fashion similar to the following example:
explain_kill_or_die(pid, sig);
SEE ALSO
kill(2) send signal to a process
explain_kill(3)
explain kill(2) errors
exit(2) terminate the calling process
COPYRIGHT
libexplain version 0.52
Copyright (C) 2009 Peter Miller
explain_kill_or_die(3)