08-10-2006
The lsp_engine - looks like a virtual machine - is the one with the problem. If the virtual memory problem started with running this app, you don't need to worry about who/what is using memory. Try to run the app as close to solo as possible.
I have not done sysadmin for long time - maybe somebody like Perderabo can give you tuning help. What I see is that you have a lot of free pagefile space.
It may also be that you will have to reconfigure the app, if that is possible.
10 More Discussions You Might Find Interesting
1. Programming
I am using gdb to examine a core file but the output contains only the method addresses in hex.
Is there anyway to translate these addresses to a human-readable form? :confused: (0 Replies)
Discussion started by: ciregbu
0 Replies
2. Programming
I am trying to print a stack trace programatically using backtrace and backtrace_symbols.
The problem is that the stack being printed in a mangled format. Is there a way to get the output in more of a human readable form?
I am using Red Hat and the program is written in c++. (2 Replies)
Discussion started by: dmirza
2 Replies
3. Shell Programming and Scripting
Hi all,
I was hoping someone can point me in the right direction. I'm trying to filter out errors from a web log- any lines with ERROR in it. I know I could simply use the grep command to do this. However, there are times when a stack trace follows the error line. I would like to capture these... (2 Replies)
Discussion started by: gswhoops
2 Replies
4. Filesystems, Disks and Memory
I'm on solaris 8. I need to check the stack trace inside my C program. I don't have printstack or walkstack. I tested getcontext and it works. But how do I get the symbols from "stack_t" ? Help please. Many thanks! (4 Replies)
Discussion started by: rydahl
4 Replies
5. Solaris
Hello ,
I use Solaris 5.10 . I have huge core file , 48 GB , resulted from an application that was running and got crashed with SIGSEGV.
On my system only mdb works. Please help me to retrieve the stack trace from this core file.
I am novice to mdb and its nuaunces. Please help me with... (2 Replies)
Discussion started by: rmv
2 Replies
6. AIX
Hi All,
I am trying to debug my core file using kdb.
When I try to get the stack trace I am facing this error.
core mapped from @ 700000000000000 to @ 70000000306fc04
Preserving 1680415 bytes of symbol table
Dump does not start with valid magic number
WARNING: Possibly truncated or... (2 Replies)
Discussion started by: Sachin1987
2 Replies
7. Shell Programming and Scripting
Hi All
Thought it would be kind of fun to implement a stack trace for a shell script that calls functions within a sub shell. This is for bash under Linux and probably not portable -
#! /bin/bash
error_exit()
{
echo "======================="
echo $1
echo... (4 Replies)
Discussion started by: steadyonabix
4 Replies
8. Programming
I have a C program which is running as daemon and has some threads.
The program is running on dual core cpu and it may happen that different threads may run on different cpu core.
The problem is sometimes it crashes with some heap memory corruption probably between threads.
GDB command(t a a... (2 Replies)
Discussion started by: rupeshkp728
2 Replies
9. Linux
Hi everyone,
Our Red Hat server hung yesterday, and I managed to log into the console and see the following message:
RIP: 0010: mwait_idle_with_hints+0x66/
0x67
RSP: 0018:ffffffff80457f40 EFLAGS: 00000046
RAX: 0000000000000010 RBX: ffff810c20075910 RCX: 0000000000000001
RDX:... (6 Replies)
Discussion started by: badoshi
6 Replies
10. Shell Programming and Scripting
I want the developers to get a mail with Java stack traces on a daily bases. When something is flaged as known issue and will get a fix but mean while this does not need to get sent each dayl. This is what I got so far. It's a bash script that runs some AWK in it.
To get the files that needs to... (6 Replies)
Discussion started by: chipmunken
6 Replies
LEARN ABOUT HPUX
pthread_default_rsestacksize_np
pthread_default_rsestacksize_np(3T) pthread_default_rsestacksize_np(3T)
NAME
pthread_default_rsestacksize_np() - change the default stacksize.
SYNOPSIS
PARAMETERS
new_size The new default register stack size.
old_size Pointer to where the old default register stack size is returned.
DESCRIPTION
The function allows an application to change the default value for the rsestacksize attribute. This function must be called before any
threads have been created. The new default stack size is passed in the new_size parameter. If not NULL, the previous default stack size
is returned in old_size. If new_size is zero, this function can be used (at any time) to query the current default stack size.
On HP-UX, threads with default stack sizes are cached after they terminate. The next time a thread is created with a default stack size, a
cached thread (and its stack) are reused. This can result in significant performance improvements for
However, if the default register stack size is not appropriate for an application, it cannot take advantage of this performance enhance-
ment. By using the function, the threads library will change the default stack size so that it matches the applications needs. This
allows the application to utilize the performance benefit of cached threads. If either of the set register stack size APIs is called the
register stack portion of the stack space will be that large instead of size determined by the implementation. The memory stack portion
will be the remainder.
RETURN VALUE
Upon successful completion, returns zero. Otherwise, an error number is returned to indicate the error (the variable is not set).
ERRORS
If any of the following occur, the function returns the corresponding error number:
The value specified by
new_size is less than register stack required for a thread.
The calling process has already created threads (this must be called
before any threads are created).
AUTHOR
was developed by HP.
SEE ALSO
pthread_attr_getstacksize(3T), pthread_attr_setstacksize(3T), pthread_default_stacksize_np(3T).
STANDARDS CONFORMANCE
Pthread Library pthread_default_rsestacksize_np(3T)