02-14-2011
Wow, great! Thanks for the help, this exactly what I was looking for!
---------- Post updated at 10:28 AM ---------- Previous update was at 10:22 AM ----------
If the limit is exceeded, does that mean the core file will not be created at all? Or will it just be truncated? I guess both wouldn't help much.
10 More Discussions You Might Find Interesting
1. Programming
Hi
I'm currently using C++ on a HP-UX 11i system (upgrading some libraries) and am encountering a problem with the process crashing when allocating memory via a call to new (a rather large array of objects are being created).
Is there a way to find out what the sizes of the stack and heap are?... (1 Reply)
Discussion started by: themezzaman
1 Replies
2. UNIX for Advanced & Expert Users
Hi,
I was logged in on a server, by ssh, with a vim open, when the battery of my laptop got empty.
When I return to the server by ssh, I can see my previous ssh session still open, and the vim process running (ttyp0). Is there a way to attach that vim to my new session (ttyp4)?
Here's part... (2 Replies)
Discussion started by: raphinou
2 Replies
3. UNIX for Advanced & Expert Users
Hi folks,
I would like to know how to hook up an xterm to another process.
Here is a high level view of what I am looking for
1. Main program starts
2. It creates an new xterm window
3. It then forks a second process & passes the xterm handle to it
4. The second process uses the second... (4 Replies)
Discussion started by: RipClaw
4 Replies
4. Solaris
Hi All,
We a critical application running on the Sun Solaris platform. But, for some reasons the process get's killed abnormally in the production environment and not sure what was causing this. I thought i would use the truss command to trace the errors.. so i used the bellow command
truss... (5 Replies)
Discussion started by: sudharma
5 Replies
5. Programming
Hey everyone,
Is there a way to make dbx break on access violations? (2 Replies)
Discussion started by: ctote
2 Replies
6. Programming
Hey everyone,
I'm trying to attach to a process that is crashing so I can debug the source code. I've tried this:
dbx -a PID
stop at "file.cpp":line#
However, nothing ever breaks. The service crashes and restarts, but I never see it hitting the code. I've tried to use a core file, but... (2 Replies)
Discussion started by: ctote
2 Replies
7. Programming
Hi everyone,
I've been struggling with this for a few weeks now. I'm trying to debug a running process with dbx on an AIX box.
The command I'm using is 'dbx -a <pid> core'
There is a function I can perform in my application that crashes this process, but it does not show up as crashed in... (0 Replies)
Discussion started by: ctote
0 Replies
8. UNIX for Dummies Questions & Answers
I'm trying to debug a service crash, and would like to break on an access violation - is this possible? (0 Replies)
Discussion started by: ctote
0 Replies
9. AIX
Hi,
I am trying to debug my project using dbx to understand the code and functionality of modules.
I compiled all my C files using gcc -g flag to enable the debug option.
I was able to get in to the debug mode using dbx.
I was able to create breakpoints using stop at line no.
"stop at... (7 Replies)
Discussion started by: Sachin1987
7 Replies
10. UNIX for Beginners Questions & Answers
Hi Team,
is there any way, I can start any process for e.g. run a shell script (infinite loop) and attach it to port 2222?
I am trying to create a scenario where an application will start running at port 2222 and I will telnet the same to confirm, application port is listening.
So,... (1 Reply)
Discussion started by: vivekpandit7
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