05-20-2014
There is not much that can be learned from truss output in a case like this. No program should ever execute an illegal instruction. When one does, it means the program in question has a bug. If this program usually works ok and this illegal instruction is a rare exception, my guess would be that the program was fed some really screwy data. The program is attempting to process data that it should reject. So I would check the program's input looking for anything really strange.
10 More Discussions You Might Find Interesting
1. Programming
Hai!
i am working on Digital UNIX V3.2c Work station, my program uses Pro*C, C and X-Motif calls. i am facing problem while running application saying "Illegal Instruction Core Dumped".
debugger dbx shows error at a line which shows "noname". when commenting large portion of the code it runs... (1 Reply)
Discussion started by: samn
1 Replies
2. UNIX for Dummies Questions & Answers
Hello
I am trying to execute a back up from one queue manager from one script saveqmgr.sh
but I am getting 2489 Illegal instruction on line 16
$ sh +x ./saveqmgr.sh S1SEAGULL
QueueManager=S1SEAGULL Retention=
S1SEAGULL.MQS.14Jan2005 not found
./saveqmgr.sh: 2836 Illegal... (1 Reply)
Discussion started by: ana
1 Replies
3. Shell Programming and Scripting
Hi
I am trying to execute a simple grep command looking for records in a filename that start with 01 (grep ^01 filename) and am getting the error Illegal instruction(coredump). Has anyone any idea why this happens? Is it due to the file being corrupted?
Thanks (1 Reply)
Discussion started by: colinmas
1 Replies
4. UNIX for Advanced & Expert Users
Hi,
this is my script to make a choice between 4 :
clear
echo " choose a profile and enter a number"
echo
echo " 1- oraSTT "
echo
echo " 2- appSTT "
echo... (3 Replies)
Discussion started by: big123456
3 Replies
5. Solaris
Hi all,
make_lofs /.cdrom/<something>/<something> 1
what does this instruction mean?
Note:both the "something" are obviously different .
I would like to know what that 1 means, the rest of the instruction is clear!!
Thanks (6 Replies)
Discussion started by: wrapster
6 Replies
6. UNIX for Dummies Questions & Answers
What's the difference between Segmentation fault and Bus error and Illegal instruction?
Sometimes I got the one, and sometimes i got another, what are their differences?
Segmentation fault (core dump)?
Bus error (core dump)?
Illegal instruction (core dump)
Thanks
Daniel (2 Replies)
Discussion started by: lakeat
2 Replies
7. UNIX for Dummies Questions & Answers
Hi All,
I am working on a Solaris 10 server. From this month start, it gives the error "logger: illegal option -- p" with each command. If I execute a script whose output shown on terminal, it comes many times.. Could you please help?
It comes only for my login. And I dont remember any changes... (4 Replies)
Discussion started by: jaiseaugustine
4 Replies
8. Shell Programming and Scripting
Hi ,
Currently the machine (solaris 10 ) is running with Sun_ssh. I would like to move to Open_ssh.
I went through google.
Each link shows different directions/ways to install openssh. I am not sure which one to follow .
Installing OpenSSH Packages - SPARC and Intel x86/Solaris 9 and... (1 Reply)
Discussion started by: frintocf
1 Replies
9. UNIX for Advanced & Expert Users
HI All ,
I am using AIX version 6 . having issue with below perl code,
sub Article ($procudure, @params) {
my ($procudure, @params) = @_;
#Get handle TO Dataware House DATABASE
try {
my $dbHandle = &Cobol::DBAccess::getDBDwConnection();
,,,,,,,,,,,,,
,,,,,,,,,,,,... (3 Replies)
Discussion started by: Perlbaby
3 Replies
10. Shell Programming and Scripting
Pleas I want answer to this question? Pleas help me
A system administrator suspects that there is an attack on his machine; he needs to make a backup of the files to check when they have been modified. For this purpose he uses the "cp -r" instruction to copy the root directory. What is the... (1 Reply)
Discussion started by: tamer11007
1 Replies
LEARN ABOUT OSX
xpc_debugger
xpc_abort(3) BSD Library Functions Manual xpc_abort(3)
NAME
xpc_abort -- conditions which cause XPC to abort
DESCRIPTION
The XPC API will aggressively defend itself against perceived misuse. Wherever XPC can definitively detect misuse of its APIs or data corrup-
tion, it will abort. For example, if the retain count of an object underflows by calling xpc_release(3) on it too many times, XPC will abort
the process.
Many frameworks opt to keep the program limping along in such a state (and will perhaps print a warning message to the system log), but
aborting upon detection provides unmistakable warning that there is a bug present in the application which should be fixed before shipping.
When XPC aborts a process, it will place information about the condition which triggered the abort in the Application Specific Information
section of the crash report. The message will be human-readable, prefixed with "XPC API Misuse:", and the crash report will indicate the
stack trace which caused the abort.
XPC will also abort if it detects unrecoverable data corruption in its internal state. The messages for these conditions will be prefixd with
"Bug in libxpc:". If you come across such a crash, please file a bug and include the generated crash log, system log and steps to reproduce
(if there are any identifiable steps).
Currently, the manner in which XPC aborts the process will result in termination due to SIGILL (illegal instruction). The exact signal raised
may change from release to release (or platform to platform). But on OS X Lion, SIGILL may be used as a hint that the process was terminated
intentionally.
DEBUGGING
When debugging in Xcode or at the gdb command prompt, the debugger acts as the exception handler for the process being debugged. As a result,
if the process is aborted by XPC, no crash report will be generated, and thus it may not be obvious why the program was terminated.
As mentioned before, SIGILL is an indication that the process was terminated intentionally. If you observe the last frame in the crashing
stack to be _xpc_api_misuse(), you may use the xpc_debugger_api_misuse_info() API from within the debugger to obtain a human-readable string
describing why the process was aborted. For example:
Program received signal EXC_BAD_INSTRUCTION, Illegal instruction/operand.
0x000000010012b25e in _xpc_api_misuse ()
(gdb) p (char *)xpc_debugger_api_misuse_info()
$1 = 0x7fff5fbff908 "XPC API Misuse: Over-release of object."
(gdb)
This message indicates that xpc_release(3) was called too many times on an object.
IMPORTANT: The xpc_debugger_api_misuse_info() API can ONLY be called from within a debugger. It is not meant to be called directly from the
program. Do not call it directly from your code, and do not rely on the address of the result for any reason.
SEE ALSO
xpc(3), xpc_object(3), xpc_objects(3)
Darwin 1 July, 2011 Darwin