08-13-2008
getting "mi_cmd_var_create: unable to create variable object" error msg
Hi,
i am working in C in Fedora Eclipse 3.3.0 with gdb debugger. I am geting segmentation fault with an error message "mi_cmd_var_create: unable to create variable object" on debugging the program.
What should I do to solve this problem?
rgds,
Dona_m
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi All,
I was able to solve my previous problem (link directory)... but now i have this following problem.
I have mounted a disk from other machine using "mount -F nfs" command. When i run a batch which generates some files in that drive.... after a certain number of files i get... (1 Reply)
Discussion started by: nileshkarania
1 Replies
2. Programming
Hi,
We are trying to run dbx on a core file for which we have the original executable and libs, but not the source / object tree. We have recompiled the objects from the original source, but dbx complains that they were compiled at a different time, and refuses to read them:
Object file:... (0 Replies)
Discussion started by: Sabari Nath S
0 Replies
3. Programming
Didn't have this problem in AIX, but ported to Linux with GCC compiler and am now getting a runtime error:
tssutil: symbol lookup error: /work/agility/devel/bin/libagam.so: undefined symbol: fstat
I'm sure most of you know that fstat is an intrinsic function just like printf, memcpy, etc. When I... (5 Replies)
Discussion started by: marcus121
5 Replies
4. Shell Programming and Scripting
Hi,
I have a perl script which is interacting with Database.
I have following line of code :
=================================================
sub BEGIN
{
#use Getopt::Std;
#getopt ('S');
#($STEAP)=($opt_S);
use lib ("/home/perl_lib");
use... (1 Reply)
Discussion started by: rawat_me01
1 Replies
5. Shell Programming and Scripting
p="-e"
echo $p
It is not returning the value "-e" stored. Instead returns null.
I am wondering how could this happen. Please help me out.I tried all possibilities like p='-e' | p="\-e". Nothing seems to work.
:confused::confused: (10 Replies)
Discussion started by: shanneykar
10 Replies
6. Solaris
I'm posting here as it didn't seem quite right in the hardware section (as it's LOM commands). My apologies if I have that wrong though :)
I've finally gotten round to configuring the LOM on my Netra X1, but I can't get it to change the hostname via the "set" command:
lom>show hostname... (2 Replies)
Discussion started by: Smiling Dragon
2 Replies
7. Shell Programming and Scripting
Hi All,
I need to get the version of python installed and store it in a variable for later use. Whereas it is printing on the console instead of storing to variable. I am able to store output of ls command in a variable. Please check the below code :
root@myhost:/volumes/srini# cat... (4 Replies)
Discussion started by: srinivasan.neel
4 Replies
8. Solaris
Hi,
I am trying to get an HPz420 workstation instaled (zfs root pool) via a jump-start server.
I have a zfs image (from this workstation) the Solaris release is 10 1/13 update 11.
I use a sparc U25 install server, upgraded to the same solaris build 10 1/13.
This server is configured to install... (8 Replies)
Discussion started by: sc0rpie
8 Replies
9. Solaris
Hello,
Each time a user log on to host, they receive below error:
-sh: /tmp/outfile: cannot create
Example:
$ ssh host
user@host's password:
Last login: Fri Dec 4 08:17:28 2015 from client.ref
|-----------------------------------------------------------------|
-sh:... (2 Replies)
Discussion started by: feroccimx
2 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