06-06-2006
These memory problems can be hard to pin down. Unless your system is actually running out of memory, quite unlikely, the problem likely occurs earlier, with an invalid free.
10 More Discussions You Might Find Interesting
1. Programming
Dear all,
I used debugger from C++ and these are the message I got:
Program received signal SIGSEGV, Segmentation fault.
0x00323fc0 in free () from /lib/tls/libc.so.6
(gdb) info s
#0 0x00323fc0 in free () from /lib/tls/libc.so.6
#1 0x00794fa1 in operator delete () from... (5 Replies)
Discussion started by: napapanbkk
5 Replies
2. AIX
Hello,
One of our customer is getting segmentation fault when he runs his shell script which invokes our executable on AIX 6.1.
On AIX 5.3, there were no issues.
Here is the truss output.
811242: __loadx(0x0A040000, 0xF0D3A26C, 0x00000000, 0x00000009, 0x00000000) = 0xF026E884... (0 Replies)
Discussion started by: erra_krishna
0 Replies
3. Cybersecurity
Hi, I installed CVSNT on PC and trying to checkout files from/on linux box.
Logging in to :pserver:user1@16.145.134.210:22/DBMONITOR/CVSROOT
CVS password:
cvs : unrecognized auth response from 16.145.134.210: SSH-2.0-OpenSSH_5.4
ssh is ok.
$ ssh user1@16.145.134.210... (1 Reply)
Discussion started by: zam
1 Replies
4. AIX
Hi to all,
i am trying to make mksysb backup of a NIM client machine from NIM master and while i am reading that the backup is done successfully i get an error message below and it doesnt exit the smit screen. also the status of the command appears to be running.
is there anybody who knows why... (3 Replies)
Discussion started by: omonoiatis9
3 Replies
5. AIX
the service coda is aborted in HPOV the OS is AIX 6.1 , i reinstall it but its give me the same message , i remove coda files under /var/opt/OV/datafiles and i restart the service but its aborted agine .
./ovc -status
ovcd OV Control CORE (44302556) Running
agtrep OV Discovery Agent... (8 Replies)
Discussion started by: thecobra151
8 Replies
6. Programming
I am making a command line program in C using XCode. When running the program, it initially does what it is supposed to do (asks me for a file path). However, when I type in a valid and existing file path, it gives me the following error:
Program received signal: “EXC_BAD_ACCESS”.... (6 Replies)
Discussion started by: mdonova33
6 Replies
7. Programming
in a single main() function,so need signal handling. Use Posix Message Queue IPC mechanism , can ignore the priority and other linked list message,to implement the scenario:
client:Knock Knock
server:who's there
client: Eric
Server:Eric,Welcome.
client:exit
all process terminated
... (1 Reply)
Discussion started by: ouou
1 Replies
8. Programming
Im using gdb and when a user disconnects from my server I receive a message
Program received signal SIGABRT, Aborted.
0x7ffe0304 in ?? ()
I was hoping someone here might have a explination for this message in gdb (26 Replies)
Discussion started by: Errigour
26 Replies
9. Solaris
hi all
I am getting following error while taking backup
using the command
ufsdump 0ubf 512 /dev/rmt/0cbn /database/backup2/rman_backup/level0 >> /database/backup2/backup_tape/level0_rman_06sep12 2>&1;
from the log i got the error
bash# tail -f level0_rman_06sep12
DUMP: Date of... (3 Replies)
Discussion started by: nikhil kasar
3 Replies
10. Programming
I am trying to learn C and while trying out some code, the program is getting aborted while I am calling free().
Here is the code:
#include <stdlib.h>
#include <stdio.h>
void print_by_ptr(char **str) {
printf("<%s>\n",*str);
printf("Now I am modifying the str.\n");
*str =... (3 Replies)
Discussion started by: chacko193
3 Replies
LEARN ABOUT LINUX
bosskill
BOSSKILL(8) System Manager's Manual BOSSKILL(8)
NAME
bosskill - send a signal to your boss, or terminate your boss
SYNOPSIS
bosskill [ -signal ] <bossname>
DESCRIPTION
bosskill sends the TERM (terminate, 15) signal to the boss with the specified bossname. If a signal name or number preceded by `-' is
given as the first argument, that signal is sent instead of terminate. The killed boss must be in the system administrator's supervisory
chain.
The following is a list of all signals with names as in the include file <signal.h>:
SIGHUP 1 hangup. Forces bossname to re-read his/her job description and figure out that he/she knows squat about sysadmin work or
life, in general.
SIGINT 2 interrupt. Prevents the bossname from interrupting the sysadmin for one hour.
SIGQUIT 3 quit. Causes the boss to quit his/her job with no explanation.
SIGILL 4 illegal instruction. Makes the boss believe the last instruction he/she gave was illegal, so he/she withdraws it.
SIGTRAP 5 trace trap. Display the exact location of the boss.
SIGABRT 6 abort. Makes the boss go home and try again tomorrow.
SIGKILL 9 kill. Game over.
SIGBUS 10 bus error. Boss's transportation fails on the way to work.
SIGSEGV 11 segmentation violation. Boss realizes he/she is trying to do something for which he/she is not quailified and stops.
SIGSYS 12 bad argument. Boss loses.
SIGPIPE 13 smoke pipe. Boss samples some green leafy substance and mellows out.
SIGALRM 14 alarm. Boss is startled and falls over. Best used when boss is walking next to his/her boss.
SIGTERM 15 termination signal. Boss is fired.
BUGS
Sending a SIGABRT to a boss that is already home will cause him/her to walk aimlessly in circles for two hours.
HISTORY
Written by Eric L. Pederson <eric@bofh.org.uk>.
27 September 1995 BOSSKILL(8)