Core Dump - Code built on 2.6 and run on 2.8

Here is a few lines of my core dump:
[1] realfree(0x4f74bd20, 0xfe8c2850, 0xfe8bc004, 0x5, 0x4f000003, 0x74bd28), at 0xfe84235c
[2] freeunlocked(0xfe8c27c4, 0xfe8bc004, 0x751b70, 0xfe8bc004, 0x7253e8, 0x0), at 0xfe842bcc
[3] free(0x751b70, 0xf0024, 0x1, 0xfedfb2c4, 0x40800, 0x0), at 0xfe842b1c
[4] CORBA::String_mgr::~String_mgr(0x728fc4, 0x2, 0xfeeeb2ac, 0xfe8bc004, 0x1, 0x4d58), at 0xfedfb2c4
We have C++ code that is built on a Solaris 2.6 platform but is being run on a Solairs 2.8 platform. The core dump occurs infrequently.
I have not printed lines below line [4] but the structure below that line looks sane. How do I go about figuring out which "string"-free is causing the crash.
Can anyone help me with sorting out the arguments on "realfree"?
Thanks.
Atul

have you tried using gdb?
gdb will let you load up the core file and bring you to the point of the crash, and then let you view the random variables and pointers' actual values...
cuz this output don't say much more than... realfree takes 6 arguments, 5 of which look to be pointers, and the 4th value i'm fairly certain is the number "5"...
with gdb you could take those 5 pointers and look in them...

Similar Messages

Core dump in _smalloc via std::valarray and __rwstd::_RW_array

Hello All,
I am developing shared libraries for Solaris 5.8 using CC v5.4 (Sun Forte 7).
These libraries are integrated with application software built with CC v5.6 (Sun Studio 9) also on Solaris 5.8.
The libraries I supply are accessed via a defined C API by the application using "dlopen".
My libraries in turn depend on other, such as libxerces, libCstd and others.
I have verified that the software libraries work correctly when run in a test harness, whether this is compiled using CC v5.4 or CC v5.6.
The application experiences the following fault:
t@4 (l@4) terminated by signal SEGV (no mapping at the fault address)
0xfeec1c98: _smalloc+0x008c: ld [%o1 + 8], %o0
The business end of the stack trace is as follows:
[5] std::valarray<double>::valarray(
[4] __rwstd::_RW_array<double>::_initial_size(
[3] operator new(0x0, ...
[2] malloc(0x1, ...
[1] _smalloc(0x8, ...
I am looking for developers with similar experiences or knowledge of this problem to try and narrow down the possible causes.
I am currently investigating the following possibilities:
Compiler patch or use -xarch=v8plus.
Inconsistent use of "-DRW_MULTI_THREAD -mt" compiler/linker options.
Incompatibility between libCstd & libstlport.
I have already referred to the following forum entries.
http://forum.java.sun.com/thread.jspa?forumID=850&threadID=5069618
http://forum.java.sun.com/thread.jspa?threadID=5071063
The code causing this core dump is in the initialisation section of the constructor of a C++ object.
class c {
public:
c(); // constructor
protected:
std:valarray m;
a::a()
// Initialisation.
: m(0) { <<<<<<<<<< The core dump occurs in the constructor of this valarray member variable.
// Constructor code.
best regards
Geoff Krechting
Edited by: Geoff.Krechting on Apr 23, 2008 5:14 AM
Edited by: Geoff.Krechting on Apr 23, 2008 7:25 AM

Both C++ 5.4 and 5.6 are End Of Life, and little support is available for them. I recommend you upgrade to Sun Studio 11, the most recent compiler that still supports Solaris 8 (which is also End Of Life). Studio 11 is free for all uses, and rebuilding your code using it should not present any problems. You can get it here:
[http://developers.sun.com/sunstudio/products/previous/11/index.jsp]
If you don't want to change compilers, you can still mix binary code from C++ 5.4 and 5.6. The rule is that you can link binaries created by an older compiler into a program or shared library built with a newer compiler, but not the other way around. That is, you need to use C++ 5.6 for all linking steps, not C++ 5.4.
The problem you are running into might be due to a compiler bug, a bug in the runtime library, or a bug in your code.
You can reduce the chances of compiler or library bugs by getting all the current patches for your compilers and libraries here:
[http://developers.sun.com/sunstudio/downloads/patches/index.jsp]
Be sure to update the C++ runtime libraries not only on the computer where you build, but on computers where the application is run.
The crash you are seeing looks like it's due to memory corruption. Memory corruption can be caused by
- using an uninitialized pointer
- using an invalid pointer:
--- points to a deleted object
--- points to an object whose lifetime has ended
- deleting an object more than once
- mis-matched new/delete operations
Using Run-Time Checking in dbx can help you find some of these problems.
% dbx myprog
% check -all
% run

Incompatibility when built in 1.4 and run in 1.3...any ideas???

We used to use the class FocusManager earlier in the code given below. It works fine when compiled and run in JDK 1.3.
When this code is compiled in 1.4 and the client runs it in 1.3 -> it throws a NoClassDefFoundError i.e. java/awt/DefaultKeyboardFocusManager
I understand the FocusManager changed in 1.4 but without backward compatibility where we are using only the abstract base class FocusManager??? Anybody faced this kind of issue. Have any ideas or workaround???
Thanks in Advance
addKeyListener(new KeyAdapter() {
public void keyPressed(KeyEvent evt) {
editor.repaint();
if (evt.getKeyCode() == KeyEvent.VK_TAB) {
evt.consume();
FocusManager f = FocusManager.getCurrentManager();
if (f != null) {
if (evt.isShiftDown())
f.focusPreviousComponent(editor);
else
f.focusNextComponent(editor);
EXCEPTION -->
Exception in thread "main" java.lang.NoClassDefFoundError: java/awt/DefaultKeyboardFocusManager
at COM.inovie.teamCenter.gui.FixedHeightText.<init>(FixedHeightText.java:36)
---------------------

True. I know... we used only FocusManager which is
present in 1.3. That is why the question. Since there
is no reference to DefaultKeyboardFocusManager in the
code, it should run the same way when we compile it in
1.3 or 1.4 Yes, there is. If you look at FocusManager in 1.4, it extends DefaultKeyboardFocusManager which didn't exist in 1.3. So, it's apparently only there for backward compatibility. If you COMPILE it using 1.3, then it may work in both 1.3 and 1.4, but if you compile it using 1.4, I'd say your out of luck.

Can you write simple Java code in a UNIX function and run it? See example....

Hi,
I'm new to Java and I have a question.
Is there any possible way a simple script like the below would work in a UNIX function called from a shell script. I know you're not supposed to do this but can you?
Thanks in advance,
javatst() {
$JAVA_HOME/bin/java <<- _java
public class HelloWorld {
public static void main(String[] args) {
System.out.println("Hello, World");
_java
javatst

2894431 wrote:
You can run a java class from a shell script like below:
#!/bin/sh
exec /usr/bin/java -DsysParam1="var1_val" -DsysParam2="var2_val" -cp jar1:jar2:jar3 /home/unixUserName/javaClasses/Test.java
exit 0
No!
This is neither a valid answer to the OPs question (since your script does not create the content of Test.java) nor working.
The java executable can only run *.class files which contain byte code of the intermediate language generated by the javac executable.
Your suggestion leads to a ClassNotFound exception.
bye
TPD

Core dump while trying to access attributes in a node using SAX

I'm running the 10g xdk with Solaris 8 and was able to get the SAX examples working. However when I tried to add some code to the example code in order to access/print out attributes, I get a core dump.
code snippet:
void MyHandler::startElementNS ( oratext* qname, oratext* local, oratext* ns_URI, NodeListRef<xmlnode>* attrs_refp)
printf( " Element: %s\n", qname);
if (attrs_refp)
for (int i=0; i<attrs_refp->getLength(); i++) <-- core dumps with getLength() call
xmlnode* node = attrs_ref->item(i);
Am I not accessing the attributes correctly? Is there an easier way to do this that I have overlooked?

I have very similar code for the parser and ran in to two problems. I am currently using 10.1.0.2.0 on Windows.
Problem 1:
Can the original poster of the following code tell me what you have under the ... section? I am trying to iterate through the attributes in attrs_refp
void MyHandler::startElementNS ( oratext* qname, oratext* local, oratext* ns_URI, NodeListRef<xmlnode>* attrs_refp)
printf( " Element: %s\n", qname);
if (attrs_refp)
for (int i=0; i<attrs_refp->getLength(); i++) <-- core dumps with getLength() call
xmlnode* node = attrs_ref->item(i);
In the ... section, I have the following line:
oratext* a = node->getname();
However, the compiler gives the following error:
error C2027: use of undefined type 'xmlnode'
Anyone have any clues as to why xmlnode is undefined?
Problem 2:
If I comment out the line oratext* a = node->getname();, I can successfully compile my program but I get a link error stating that both the methods item() and getLength() are unresolved external symbols. This lead me to believe these methods are not implemented in the Oracle XDK. user457758 seems to have gotten past this stage as he is getting a run time error so the compilation appears to be successful. I assume user457758 is using the latest 10.1.0.3.0 available on Solaris instead of 10.1.0.2.0 that I am currently using on Windows. Did anyone experience similar compilation errors?
Thanks for any help/info in advance.

Python crashes. Core dump inside xcurses2/tgetent(): cur_term is nil

I tried to build latest Python sources with Sun C compiler on Solaris snv_145 (sparc or x86)
There is no issue to build the binary, but then Python's
harness runs it as: 'python -E ./setup.py build' it core dumps.
Actually, Python's version and Sun compiler versions are not essential.
I tried viariety of them, and all produce the same core dump.
I ran dbx with this and pinpointed the place:
At some moment python binary calls rlinit_terminal_io() from
open source readline.so library, which in turn invokes kernel's tgetent()
function from libcurses.so.2. That tgetent() function crashes on the
following line where cur_term is nil:
if (strcmp(cur_term->_term, name) == 0)
The top of crashed stack looks like this:
========================
t@1 (l@1) signal SEGV (no mapping at the fault address) in tgetent at line 65 in file "tgetent.c"
65 if (strcmp(cur_term->_term, name) == 0)
(dbx) print name
name = 0x8047a4d "sun-cmd"
(dbx) print cur_term
cur_term = (nil)
(dbx) where
current thread: t@1
=>[1] tgetent(buffer = 0x8786dd0 "", name = 0x8047a4d "sun-cmd"), line 65 in "tgetent.c"
[2] rlinit_terminal_io(terminal_name = 0x8047a4d "sun-cmd"), line 460 in "terminal.c"
[3] readline_initialize_everything(), line 1066 in "readline.c"
[4] rl_initialize(), line 968 in "readline.c"
[5] setup_readline(), line 884 in "readline.c"
[6] PyInit_readline(), line 1133 in "readline.c"
[7] PyImportLoadDynamicModule(name = 0x8747698 "readline", pathname = 0x8656e38 "build/lib.solaris-2.11-i86pc-3.2-pydebug/readline.so", fp = (nil)), line 57 in "importdl.c"
===================
May be to prevent this crash I need to define some
environment variable which ultimately will initialize 'cur_term' global?
Please advise.

Please edit your post and use code tags when posting logs and error messages to the boards:
https://wiki.archlinux.org/index.php/Fo … s_and_Code
As to your errors, this is documented in the wiki:
https://wiki.archlinux.org/index.php/Pa … stem.22.21

Linux Core Dump

Today was the first time I have tried running a Java app from a script file within Red Hat Linux 6.2. I am using the 1.3.1 SDK SE. Before now, all classes were run in the JVM created by my servlet engine (Apache Tomcat). Now that I have an application to start and run in it's own JVM, I get an immediate core dump. Everything works fine in Windows using JBuilder. Copied the class files to Linux, created a shell script that sets the JAVA_HOME PATH and CLASSPATH correctly based on the one JBuilder uses. Call java and specify my class name. Immediate core dump. I have even tried to run it as root. What should I check? Is there a way to see what error it is running into? I am kind of stumped since there is no error on the screen and I wouldn't know what to do with a core file.

To simplify matters, I have created a test class that all it does is System.out.println. I still get a core dump. Here is the shell file I use to run it.
#!/bin/sh
JAVA_HOME=/usr/java/jdk1.3.1
PATH=.:$PATH:$JAVA_HOME/bin
TOMCAT_HOME=/usr/jakarta-tomcat-3.2.2
CLASSPATH=.:/home/web/HB/classes:/home/web/HD/WEB-INF/classes:$TOMCAT_HOME/lib/classes12.jar:$JAVA_HOME/jre/lib/rt.jar:$JAVA_HOME/jre/lib/i18n.jar:$JAVA_HOME/lib/tools.jar
export JAVA_HOME PATH TOMCAT_HOME CLASSPATH
java test.Test

Java Core Dump

Hi all
We have some problems on our production system that it keeps on dumping core dumps of about 3gigs each night and just kills the system. Looks like something wrong with java?
Directory: /usr/sap/<SID>/DVEBMGS00/j2ee/cluster/server0
Files:
core.20090817.174103.15073438.0009.dmp
Snap.20090817.174103.15073438.0010.trc
heapdump.20090817.174103.15073438.0011.phd
javacore.20090817.174103.15073438.0012.txt
2.49    core.20090817.161324.15073438.0001.dmp
2.53    core.20090817.163951.15073438.0005.dmp
2.58    core.20090817.174103.15073438.0009.dmp
Any help will be much appreciated.

Hello Stephan
Most likely these dumps are being caused by an OutOfMemoryError in the java stack. Check note #1289240 How to deal with out of memory errors, for some hints on what to do.
Regards
Mark

Java Core Dump Debug

Hi,
One of my Java Processes on Solaris Core Dumped due to SIGNAL 11 (SIGENV) and SIGNAL 10 (SIGBUS). SIgnal 11 is caused due to a Segmentation fault and Signal 10 is caused due to a 'Bus error' (hardware error).
I would like to know, which is the best debugger to debug this core dump (java) and know the root cause. I tried 'gdb' but I am not sure if 'gdb' works for java. I would like to get a neat stack trace of the error.
Any help is appreciated.
Thanks.

Check out this page: http://www-128.ibm.com/developerworks/java/library/j-jnidebug/index.html

How to create a virtual FPGA and run LabVIEW code on it?

Hi
I am new to LabVIEW FPGA world. I have code written in LV 8.6 that was running on a Virtex 5. I need to run this code on a virtual FPGA but I need this to be as real as possible and maybe to acces this virtual FPGA also from another environment. Do you think this can be done? I need just a general answer to have an idea on this problem.
Thanks

If I've understood correctly, you have LabVIEW code written for an FPGA and running on an NI FPGA board, which you'd now like to run in a simulated system. I doubt this is possible since I don't think there is a way for you to simulate all the hardware (DAQ and whatever else) that is attached to the FPGA on the real hardware. Also, LabVIEW doesn't have any way of accessing an arbitrary non-NI FPGA target and without the LabVIEW interface I don't think your FPGA code will be too useful.

Core dump (WL - 4.5 and Solaris 7)

We are using WebLogic 4.5 on Solaris 7. Some times the WebLogic dumps core and exits. There is no pattern for it. I am attaching the core generated:
Could there be a solution some one knows of.
Thanks.
-manish
kghalo bad size 0x15330128
********** Internal heap ERROR KGHALO2 addr=0x0 *********
HEAP DUMP heap name="Alloc environm" desc=0x37083f4
extent sz=0x1024 alt=32 het=32767 rec=0 flg=3 opc=2
parent=0 owner=0 nex=0 xsz=0x17a0
EXTENT 0
Chunk 3daff00 sz= 6040 free " "
EXTENT 1
Chunk 4a857b8 sz= 12040 free " "
EXTENT 2
Chunk 3eaac98 sz= 6372 free " "
EXTENT 3
Chunk 3dacfe8 sz= 12040 free " "
EXTENT 4
Chunk 37567a0 sz= 4660 free " "
Chunk 37579d4 sz= 4144 recreate "Alloc statemen " latch=0
ds 3758d70 sz= 4144 ct= 1
Chunk 3758a04 sz= 1080 freeable assoc with mark prv=0 nxt=0
Chunk 3758e3c sz= 4144 recreate "Alloc statemen " latch=0
ds 375a1d8 sz= 4144 ct= 1
Chunk 3759e6c sz= 1080 freeable assoc with mark prv=0 nxt=0
Chunk 375a2a4 sz= 28 freeable assoc with mark prv=0 nxt=0
Chunk 375a2c0 sz= 5224 free " "
Chunk 375b728 sz= 20 freeable assoc with mark prv=0 nxt=0
Chunk 375b73c sz= 20 freeable assoc with mark prv=0 nxt=0
Chunk 375b750 sz= 256 freeable assoc with mark prv=0 nxt=0
EXTENT 5
Chunk 404b50 sz= 13328 freeable "Alloc server h " ds=3709408
EXTENT 6
Chunk 3708980 sz= 40 perm "perm " alo=40
Chunk 37089a8 sz= 2212 recreate "Alloc server h " latch=0
ds 3709408 sz= 15540 ct= 2
404b50 sz= 13328
Chunk 370924c sz= 104 freeable assoc with mark prv=0 nxt=0
Chunk 37092b4 sz= 444 freeable assoc with mark prv=0 nxt=0
Chunk 3709470 sz= 1308 freeable assoc with mark prv=0 nxt=0
Total heap size = 74584
FREE LISTS:
Bucket 0 size=272
Bucket 1 size=528
Bucket 2 size=1040
Chunk 37567a0 sz= 4660 free " "
Chunk 3dacfe8 sz= 12040 free " "
Chunk 3eaac98 sz= 6372 free " "
Chunk 4a857b8 sz= 12040 free " "
Chunk 3daff00 sz= 6040 free " "
Chunk 375a2c0 sz= 5224 free " "
Total free space = 46376
UNPINNED RECREATABLE CHUNKS (lru first):
PERMANENT CHUNKS:
Chunk 3708980 sz= 40 perm "perm " alo=40
Permanent space = 40
Hla: 0
kgepop: no error frame to pop to for error 0
Segmentation Fault
si_signo [11]: Segmentation Fault
si_errno [0]: Error 0
si_code [1]: SEGV_MAPERR [addr: 0x0]
stackpointer=F9FBFC50
"SSLListenThread" (TID:0x3a8b58c, sys_thread_t:0x3a8b510, state:R, thread_t: t@30, threadID:0xf8d91dc8, stack_bottom:0xf8d92000, sta
ck_size:0x20000) prio=5
[1] java.net.PlainSocketImpl.socketAccept(Native Method)
[2] java.net.PlainSocketImpl.accept(PlainSocketImpl.java:406)
[3] java.net.ServerSocket.implAccept(ServerSocket.java:241)
[4] java.net.ServerSocket.accept(ServerSocket.java:224)
[5] weblogic.security.SSL.SSLServerSocket.acceptNoHandshake(SSLServerSocket.java:121)
[6] weblogic.security.SSL.SSLServerSocket.accept(SSLServerSocket.java:112)
[7] weblogic.t3.srvr.ListenThread.run(ListenThread.java:277)
"ListenThread" (TID:0x3a7b294, sys_thread_t:0x3a7b218, state:R, thread_t: t@29, threadID:0xf8e41dc8, stack_bottom:0xf8e42000, stack_
size:0x20000) prio=5
[1] java.net.PlainSocketImpl.socketAccept(Native Method)
[2] java.net.PlainSocketImpl.accept(PlainSocketImpl.java:406)
[3] java.net.ServerSocket.implAccept(ServerSocket.java:241)
[4] java.net.ServerSocket.accept(ServerSocket.java:224)
[5] weblogic.t3.srvr.ListenThread.run(ListenThread.java:277)
"ExecuteThread-14" (TID:0x54e104, sys_thread_t:0x54e088, state:MW, thread_t: t@25, threadID:0xf8eb1dc8, stack_bottom:0xf8eb2000, sta
ck_size:0x20000) prio=5
[1] weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:269)
[2] weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
[3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
"ExecuteThread-13" (TID:0x59c504, sys_thread_t:0x59c488, state:R, thread_t: t@24, threadID:0xf8ee1dc8, stack_bottom:0xf8ee2000, stac
k_size:0x20000) prio=5
[1] weblogic.socket.PosixSocketMuxer.poll(Native Method)
[2] weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:270)
[3] weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
[4] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
"ExecuteThread-12" (TID:0x5ba504, sys_thread_t:0x5ba488, state:MW, thread_t: t@23, threadID:0xf8f11dc8, stack_bottom:0xf8f12000, sta
ck_size:0x20000) prio=5
[1] weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:269)
[2] weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
[3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
"ExecuteThread-11" (TID:0x4f62ec, sys_thread_t:0x4f6270, state:CW, thread_t: t@22, threadID:0xf8f41dc8, stack_bottom:0xf8f42000, sta
ck_size:0x20000) prio=5
[1] java.lang.Object.wait(Native Method)
[2] java.lang.Object.wait(Object.java:424)
[3] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:90)
[4] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
"ExecuteThread-10" (TID:0x52810c, sys_thread_t:0x528090, state:CW, thread_t: t@21, threadID:0xf8f71dc8, stack_bottom:0xf8f72000, sta
ck_size:0x20000) prio=5
[1] java.lang.Object.wait(Native Method)
[2] java.lang.Object.wait(Object.java:424)
[3] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:90)
[4] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
"ExecuteThread-9" (TID:0x53050c, sys_thread_t:0x530490, state:CW, thread_t: t@20, threadID:0xf9171dc8, stack_bottom:0xf9172000, stac
k_size:0x20000) prio=5
[1] java.lang.Object.wait(Native Method)
[2] java.lang.Object.wait(Object.java:424)
[3] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:90)
[4] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
"ExecuteThread-8" (TID:0x53210c, sys_thread_t:0x532090, state:CW, thread_t: t@19, threadID:0xf9e61dc8, stack_bottom:0xf9e62000, stac
k_size:0x20000) prio=5
[1] java.lang.Object.wait(Native Method)
[2] java.lang.Object.wait(Object.java:424)
[3] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:90)
[4] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
"ExecuteThread-7" (TID:0x55ed3c, sys_thread_t:0x55ecc0, state:CW, thread_t: t@18, threadID:0xf9e91dc8, stack_bottom:0xf9e92000, stac
k_size:0x20000) prio=5
[1] java.lang.Object.wait(Native Method)
[2] java.lang.Object.wait(Object.java:424)
[3] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:90)
[4] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
"ExecuteThread-6" (TID:0x5c750c, sys_thread_t:0x5c7490, state:CW, thread_t: t@17, threadID:0xf9ec1dc8, stack_bottom:0xf9ec2000, stac
k_size:0x20000) prio=5
[1] java.lang.Object.wait(Native Method)
[2] java.lang.Object.wait(Object.java:424)
[3] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:90)
[4] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
"ExecuteThread-5" (TID:0x5cc514, sys_thread_t:0x5cc498, state:CW, thread_t: t@16, threadID:0xf9ef1dc8, stack_bottom:0xf9ef2000, stac
k_size:0x20000) prio=5
[1] java.lang.Object.wait(Native Method)
[2] java.lang.Object.wait(Object.java:424)
[3] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:90)
[4] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
"ExecuteThread-4" (TID:0x5d091c, sys_thread_t:0x5d08a0, state:R, thread_t: t@15, threadID:0xf9fc1dc8, stack_bottom:0xf9fc2000, stack
_size:0x20000) prio=5 current thread
[1] weblogic.db.oci.OciCursor.exec(Native Method)
[2] weblogic.db.oci.OciCursor.oci_exec(OciCursor.java:1823)
[3] weblogic.jdbcbase.oci.Statement.executeUpdate(Statement.java:846)
[4] weblogic.jdbcbase.oci.Statement.execute(Statement.java:1361)
[5] weblogic.jdbc20.pool.PreparedStatement.execute(PreparedStatement.java:27)
[6] weblogic.jdbc20.rmi.internal.PreparedStatementImpl.execute(PreparedStatementImpl.java:288)
[7] weblogic.jdbc20.rmi.SerialPreparedStatement.execute(SerialPreparedStatement.java:401)
[8] com.ebd.oss.isp.model.ISPModel.getContactInfo(ISPModel.java:242)
[9] com.ebd.oss.isp.model.ISPModel.getISPInfoByID(ISPModel.java:634)
[10] jsp_servlet._ruUpdateContact._jspService(_ruUpdateContact.java:110)
[11] weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
[12] weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:105)
[13] weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:240)
[14] weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:161)
[15] jsp_servlet._Template._jspService(_Template.java:106)
[16] weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
[17] weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:105)
[18] weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:143)
[19] jsp_servlet._Main._jspService(_Main.java:204)
[20] weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
[21] weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:105)
[22] weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:742)
[23] weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:686)
[24] weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:247)
[25] weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:361)
[26] weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:261)
[27] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
"ExecuteThread-3" (TID:0x5c7934, sys_thread_t:0x5c78b8, state:CW, thread_t: t@14, threadID:0xf9ff1dc8, stack_bottom:0xf9ff2000, stac
k_size:0x20000) prio=5
[1] java.lang.Object.wait(Native Method)
[2] java.lang.Object.wait(Object.java:424)
[3] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:90)
[4] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
"ExecuteThread-2" (TID:0x5cb534, sys_thread_t:0x5cb4b8, state:CW, thread_t: t@13, threadID:0xfe041dc8, stack_bottom:0xfe042000, stac
k_size:0x20000) prio=5
[1] java.lang.Object.wait(Native Method)
[2] java.lang.Object.wait(Object.java:424)
[3] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:90)
[4] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
"ExecuteThread-1" (TID:0x5d1534, sys_thread_t:0x5d14b8, state:CW, thread_t: t@12, threadID:0xfe071dc8, stack_bottom:0xfe072000, stac
k_size:0x20000) prio=5
[1] java.lang.Object.wait(Native Method)
[2] java.lang.Object.wait(Object.java:424)
[3] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:90)
[4] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
"ExecuteThread-0" (TID:0x5d1a2c, sys_thread_t:0x5d19b0, state:CW, thread_t: t@11, threadID:0xfe0a1dc8, stack_bottom:0xfe0a2000, stac
k_size:0x20000) prio=5
[1] java.lang.Object.wait(Native Method)
[2] java.lang.Object.wait(Object.java:424)
[3] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:90)
[4] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
"TimeEventGenerator" (TID:0x599694, sys_thread_t:0x599618, state:CW, thread_t: t@10, threadID:0xfe0d1dc8, stack_bottom:0xfe0d2000, s
tack_size:0x20000) prio=5
[1] java.lang.Object.wait(Native Method)
[2] weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:252)
[3] weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java:141)
[4] java.lang.Thread.run(Thread.java:485)
"SpinnerRandomSource" (TID:0x55f2a4, sys_thread_t:0x55f228, state:CW, thread_t: t@8, threadID:0xfec41dc8, stack_bottom:0xfec42000, s
tack_size:0x20000) prio=5
[1] java.lang.Object.wait(Native Method)
[2] java.lang.Object.wait(Object.java:424)
[3] weblogic.security.SpinnerThread.stopSpinning(SpinnerRandomBitsSource.java:104)
[4] weblogic.security.SpinnerThread.run(SpinnerRandomBitsSource.java:121)
Exiting Thread (sys_thread_t:0xff2cace0) : no stack
"Finalizer" (TID:0x172e84, sys_thread_t:0x172e08, state:CW, thread_t: t@6, threadID:0xfed31dc8, stack_bottom:0xfed32000, stack_size:
0x20000) prio=8
[1] java.lang.Object.wait(Native Method)
[2] java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:113)
[3] java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:128)
[4] java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:175)
"Reference Handler" (TID:0x16ed54, sys_thread_t:0x16ecd8, state:CW, thread_t: t@5, threadID:0xfed61dc8, stack_bottom:0xfed62000, sta
ck_size:0x20000) prio=10
[1] java.lang.Object.wait(Native Method)
[2] java.lang.Object.wait(Object.java:424)
[3] java.lang.ref.Reference$ReferenceHandler.run(Reference.java:115)
"Signal dispatcher" (TID:0x14e1e4, sys_thread_t:0x14e168, state:MW, thread_t: t@4, threadID:0xfed91dc8, stack_bottom:0xfed92000, sta
ck_size:0x20000) prio=10
"main" (TID:0x39974, sys_thread_t:0x398f8, state:CW, thread_t: t@1, threadID:0x24ac8, stack_bottom:0xffbf0000, stack_size:0x20000) p
rio=5
[1] java.lang.Object.wait(Native Method)
[2] java.lang.Object.wait(Object.java:424)
[3] weblogic.t3.srvr.T3Srvr.waitForDeath(T3Srvr.java:1791)
[4] java.lang.reflect.Method.invoke(Native Method)
[5] weblogic.Server.startServerDynamically(Server.java:107)
[6] weblogic.Server.main(Server.java:65)
[7] weblogic.Server.main(Server.java:55)
Abort - core dumped

The current thread shows JVM has core dumped on a native OCI call.
Type-2 drivers need to make OCI calls to connect to the Database server and since OCI calls are in C,
there is a possibility that C code is causing JVM to crash.
I would recommend you to give it a try with type-4 driver and see if you can get rid of core dumps.
Kumar
manish wrote:
We are using WebLogic 4.5 on Solaris 7. Some times the WebLogic dumps core and exits. There is no pattern for it. I am attaching the core generated:
Could there be a solution some one knows of.
Thanks.
-manish
kghalo bad size 0x15330128
********** Internal heap ERROR KGHALO2 addr=0x0 *********
HEAP DUMP heap name="Alloc environm" desc=0x37083f4
extent sz=0x1024 alt=32 het=32767 rec=0 flg=3 opc=2
parent=0 owner=0 nex=0 xsz=0x17a0
EXTENT 0
Chunk 3daff00 sz= 6040 free " "
EXTENT 1
Chunk 4a857b8 sz= 12040 free " "
EXTENT 2
Chunk 3eaac98 sz= 6372 free " "
EXTENT 3
Chunk 3dacfe8 sz= 12040 free " "
EXTENT 4
Chunk 37567a0 sz= 4660 free " "
Chunk 37579d4 sz= 4144 recreate "Alloc statemen " latch=0
ds 3758d70 sz= 4144 ct= 1
Chunk 3758a04 sz= 1080 freeable assoc with mark prv=0 nxt=0
Chunk 3758e3c sz= 4144 recreate "Alloc statemen " latch=0
ds 375a1d8 sz= 4144 ct= 1
Chunk 3759e6c sz= 1080 freeable assoc with mark prv=0 nxt=0
Chunk 375a2a4 sz= 28 freeable assoc with mark prv=0 nxt=0
Chunk 375a2c0 sz= 5224 free " "
Chunk 375b728 sz= 20 freeable assoc with mark prv=0 nxt=0
Chunk 375b73c sz= 20 freeable assoc with mark prv=0 nxt=0
Chunk 375b750 sz= 256 freeable assoc with mark prv=0 nxt=0
EXTENT 5
Chunk 404b50 sz= 13328 freeable "Alloc server h " ds=3709408
EXTENT 6
Chunk 3708980 sz= 40 perm "perm " alo=40
Chunk 37089a8 sz= 2212 recreate "Alloc server h " latch=0
ds 3709408 sz= 15540 ct= 2
404b50 sz= 13328
Chunk 370924c sz= 104 freeable assoc with mark prv=0 nxt=0
Chunk 37092b4 sz= 444 freeable assoc with mark prv=0 nxt=0
Chunk 3709470 sz= 1308 freeable assoc with mark prv=0 nxt=0
Total heap size = 74584
FREE LISTS:
Bucket 0 size=272
Bucket 1 size=528
Bucket 2 size=1040
Chunk 37567a0 sz= 4660 free " "
Chunk 3dacfe8 sz= 12040 free " "
Chunk 3eaac98 sz= 6372 free " "
Chunk 4a857b8 sz= 12040 free " "
Chunk 3daff00 sz= 6040 free " "
Chunk 375a2c0 sz= 5224 free " "
Total free space = 46376
UNPINNED RECREATABLE CHUNKS (lru first):
PERMANENT CHUNKS:
Chunk 3708980 sz= 40 perm "perm " alo=40
Permanent space = 40
Hla: 0
kgepop: no error frame to pop to for error 0
Segmentation Fault
si_signo [11]: Segmentation Fault
si_errno [0]: Error 0
si_code [1]: SEGV_MAPERR [addr: 0x0]
stackpointer=F9FBFC50
"SSLListenThread" (TID:0x3a8b58c, sys_thread_t:0x3a8b510, state:R, thread_t: t@30, threadID:0xf8d91dc8, stack_bottom:0xf8d92000, sta
ck_size:0x20000) prio=5
[1] java.net.PlainSocketImpl.socketAccept(Native Method)
[2] java.net.PlainSocketImpl.accept(PlainSocketImpl.java:406)
[3] java.net.ServerSocket.implAccept(ServerSocket.java:241)
[4] java.net.ServerSocket.accept(ServerSocket.java:224)
[5] weblogic.security.SSL.SSLServerSocket.acceptNoHandshake(SSLServerSocket.java:121)
[6] weblogic.security.SSL.SSLServerSocket.accept(SSLServerSocket.java:112)
[7] weblogic.t3.srvr.ListenThread.run(ListenThread.java:277)
"ListenThread" (TID:0x3a7b294, sys_thread_t:0x3a7b218, state:R, thread_t: t@29, threadID:0xf8e41dc8, stack_bottom:0xf8e42000, stack_
size:0x20000) prio=5
[1] java.net.PlainSocketImpl.socketAccept(Native Method)
[2] java.net.PlainSocketImpl.accept(PlainSocketImpl.java:406)
[3] java.net.ServerSocket.implAccept(ServerSocket.java:241)
[4] java.net.ServerSocket.accept(ServerSocket.java:224)
[5] weblogic.t3.srvr.ListenThread.run(ListenThread.java:277)
"ExecuteThread-14" (TID:0x54e104, sys_thread_t:0x54e088, state:MW, thread_t: t@25, threadID:0xf8eb1dc8, stack_bottom:0xf8eb2000, sta
ck_size:0x20000) prio=5
[1] weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:269)
[2] weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
[3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
"ExecuteThread-13" (TID:0x59c504, sys_thread_t:0x59c488, state:R, thread_t: t@24, threadID:0xf8ee1dc8, stack_bottom:0xf8ee2000, stac
k_size:0x20000) prio=5
[1] weblogic.socket.PosixSocketMuxer.poll(Native Method)
[2] weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:270)
[3] weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
[4] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
"ExecuteThread-12" (TID:0x5ba504, sys_thread_t:0x5ba488, state:MW, thread_t: t@23, threadID:0xf8f11dc8, stack_bottom:0xf8f12000, sta
ck_size:0x20000) prio=5
[1] weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:269)
[2] weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
[3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
"ExecuteThread-11" (TID:0x4f62ec, sys_thread_t:0x4f6270, state:CW, thread_t: t@22, threadID:0xf8f41dc8, stack_bottom:0xf8f42000, sta
ck_size:0x20000) prio=5
[1] java.lang.Object.wait(Native Method)
[2] java.lang.Object.wait(Object.java:424)
[3] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:90)
[4] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
"ExecuteThread-10" (TID:0x52810c, sys_thread_t:0x528090, state:CW, thread_t: t@21, threadID:0xf8f71dc8, stack_bottom:0xf8f72000, sta
ck_size:0x20000) prio=5
[1] java.lang.Object.wait(Native Method)
[2] java.lang.Object.wait(Object.java:424)
[3] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:90)
[4] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
"ExecuteThread-9" (TID:0x53050c, sys_thread_t:0x530490, state:CW, thread_t: t@20, threadID:0xf9171dc8, stack_bottom:0xf9172000, stac
k_size:0x20000) prio=5
[1] java.lang.Object.wait(Native Method)
[2] java.lang.Object.wait(Object.java:424)
[3] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:90)
[4] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
"ExecuteThread-8" (TID:0x53210c, sys_thread_t:0x532090, state:CW, thread_t: t@19, threadID:0xf9e61dc8, stack_bottom:0xf9e62000, stac
k_size:0x20000) prio=5
[1] java.lang.Object.wait(Native Method)
[2] java.lang.Object.wait(Object.java:424)
[3] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:90)
[4] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
"ExecuteThread-7" (TID:0x55ed3c, sys_thread_t:0x55ecc0, state:CW, thread_t: t@18, threadID:0xf9e91dc8, stack_bottom:0xf9e92000, stac
k_size:0x20000) prio=5
[1] java.lang.Object.wait(Native Method)
[2] java.lang.Object.wait(Object.java:424)
[3] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:90)
[4] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
"ExecuteThread-6" (TID:0x5c750c, sys_thread_t:0x5c7490, state:CW, thread_t: t@17, threadID:0xf9ec1dc8, stack_bottom:0xf9ec2000, stac
k_size:0x20000) prio=5
[1] java.lang.Object.wait(Native Method)
[2] java.lang.Object.wait(Object.java:424)
[3] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:90)
[4] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
"ExecuteThread-5" (TID:0x5cc514, sys_thread_t:0x5cc498, state:CW, thread_t: t@16, threadID:0xf9ef1dc8, stack_bottom:0xf9ef2000, stac
k_size:0x20000) prio=5
[1] java.lang.Object.wait(Native Method)
[2] java.lang.Object.wait(Object.java:424)
[3] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:90)
[4] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
"ExecuteThread-4" (TID:0x5d091c, sys_thread_t:0x5d08a0, state:R, thread_t: t@15, threadID:0xf9fc1dc8, stack_bottom:0xf9fc2000, stack
_size:0x20000) prio=5 current thread
[1] weblogic.db.oci.OciCursor.exec(Native Method)
[2] weblogic.db.oci.OciCursor.oci_exec(OciCursor.java:1823)
[3] weblogic.jdbcbase.oci.Statement.executeUpdate(Statement.java:846)
[4] weblogic.jdbcbase.oci.Statement.execute(Statement.java:1361)
[5] weblogic.jdbc20.pool.PreparedStatement.execute(PreparedStatement.java:27)
[6] weblogic.jdbc20.rmi.internal.PreparedStatementImpl.execute(PreparedStatementImpl.java:288)
[7] weblogic.jdbc20.rmi.SerialPreparedStatement.execute(SerialPreparedStatement.java:401)
[8] com.ebd.oss.isp.model.ISPModel.getContactInfo(ISPModel.java:242)
[9] com.ebd.oss.isp.model.ISPModel.getISPInfoByID(ISPModel.java:634)
[10] jsp_servlet._ruUpdateContact._jspService(_ruUpdateContact.java:110)
[11] weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
[12] weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:105)
[13] weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:240)
[14] weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:161)
[15] jsp_servlet._Template._jspService(_Template.java:106)
[16] weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
[17] weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:105)
[18] weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:143)
[19] jsp_servlet._Main._jspService(_Main.java:204)
[20] weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
[21] weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:105)
[22] weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:742)
[23] weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:686)
[24] weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:247)
[25] weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:361)
[26] weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:261)
[27] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
"ExecuteThread-3" (TID:0x5c7934, sys_thread_t:0x5c78b8, state:CW, thread_t: t@14, threadID:0xf9ff1dc8, stack_bottom:0xf9ff2000, stac
k_size:0x20000) prio=5
[1] java.lang.Object.wait(Native Method)
[2] java.lang.Object.wait(Object.java:424)
[3] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:90)
[4] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
"ExecuteThread-2" (TID:0x5cb534, sys_thread_t:0x5cb4b8, state:CW, thread_t: t@13, threadID:0xfe041dc8, stack_bottom:0xfe042000, stac
k_size:0x20000) prio=5
[1] java.lang.Object.wait(Native Method)
[2] java.lang.Object.wait(Object.java:424)
[3] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:90)
[4] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
"ExecuteThread-1" (TID:0x5d1534, sys_thread_t:0x5d14b8, state:CW, thread_t: t@12, threadID:0xfe071dc8, stack_bottom:0xfe072000, stac
k_size:0x20000) prio=5
[1] java.lang.Object.wait(Native Method)
[2] java.lang.Object.wait(Object.java:424)
[3] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:90)
[4] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
"ExecuteThread-0" (TID:0x5d1a2c, sys_thread_t:0x5d19b0, state:CW, thread_t: t@11, threadID:0xfe0a1dc8, stack_bottom:0xfe0a2000, stac
k_size:0x20000) prio=5
[1] java.lang.Object.wait(Native Method)
[2] java.lang.Object.wait(Object.java:424)
[3] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:90)
[4] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
"TimeEventGenerator" (TID:0x599694, sys_thread_t:0x599618, state:CW, thread_t: t@10, threadID:0xfe0d1dc8, stack_bottom:0xfe0d2000, s
tack_size:0x20000) prio=5
[1] java.lang.Object.wait(Native Method)
[2] weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:252)
[3] weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java:141)
[4] java.lang.Thread.run(Thread.java:485)
"SpinnerRandomSource" (TID:0x55f2a4, sys_thread_t:0x55f228, state:CW, thread_t: t@8, threadID:0xfec41dc8, stack_bottom:0xfec42000, s
tack_size:0x20000) prio=5
[1] java.lang.Object.wait(Native Method)
[2] java.lang.Object.wait(Object.java:424)
[3] weblogic.security.SpinnerThread.stopSpinning(SpinnerRandomBitsSource.java:104)
[4] weblogic.security.SpinnerThread.run(SpinnerRandomBitsSource.java:121)
Exiting Thread (sys_thread_t:0xff2cace0) : no stack
"Finalizer" (TID:0x172e84, sys_thread_t:0x172e08, state:CW, thread_t: t@6, threadID:0xfed31dc8, stack_bottom:0xfed32000, stack_size:
0x20000) prio=8
[1] java.lang.Object.wait(Native Method)
[2] java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:113)
[3] java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:128)
[4] java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:175)
"Reference Handler" (TID:0x16ed54, sys_thread_t:0x16ecd8, state:CW, thread_t: t@5, threadID:0xfed61dc8, stack_bottom:0xfed62000, sta
ck_size:0x20000) prio=10
[1] java.lang.Object.wait(Native Method)
[2] java.lang.Object.wait(Object.java:424)
[3] java.lang.ref.Reference$ReferenceHandler.run(Reference.java:115)
"Signal dispatcher" (TID:0x14e1e4, sys_thread_t:0x14e168, state:MW, thread_t: t@4, threadID:0xfed91dc8, stack_bottom:0xfed92000, sta
ck_size:0x20000) prio=10
"main" (TID:0x39974, sys_thread_t:0x398f8, state:CW, thread_t: t@1, threadID:0x24ac8, stack_bottom:0xffbf0000, stack_size:0x20000) p
rio=5
[1] java.lang.Object.wait(Native Method)
[2] java.lang.Object.wait(Object.java:424)
[3] weblogic.t3.srvr.T3Srvr.waitForDeath(T3Srvr.java:1791)
[4] java.lang.reflect.Method.invoke(Native Method)
[5] weblogic.Server.startServerDynamically(Server.java:107)
[6] weblogic.Server.main(Server.java:65)
[7] weblogic.Server.main(Server.java:55)
Abort - core dumped

JVM core dump - JNI code

I am using JNI in my Java application , 12 hours after running my test case get a JVM crash -
1) These are the parameters with which i invoke my Java program
java -d64 -Xcheck:jni -Xmx2560M -Xms2560M -Xss256k RunQueries
2) The Heap output at the time of the core shows "from space" as 100% used , does this signify anything?
Heap at VM Abort:
Heap
def new generation total 848128K, used 672342K [0xfffffffe93c00000, 0xfffffffec9150000, 0xfffffffec9150000)
eden space 822464K, 78% used [0xfffffffe93c00000, 0xfffffffebb385b90, 0xfffffffec5f30000)
from space 25664K, 100% used [0xfffffffec7840000, 0xfffffffec9150000, 0xfffffffec9150000)
to space 25664K, 0% used [0xfffffffec5f30000, 0xfffffffec5f30000, 0xfffffffec7840000)
tenured generation total 1747648K, used 1350866K [0xfffffffec9150000, 0xffffffff33c00000, 0xffffffff33c00000)
the space 1747648K, 77% used [0xfffffffec9150000, 0xffffffff1b884830, 0xffffffff1b884a00, 0xffffffff33c00000)
compacting perm gen total 16384K, used 13550K [0xffffffff33c00000, 0xffffffff34c00000, 0xffffffff37c00000)
the space 16384K, 82% used [0xffffffff33c00000, 0xffffffff3493b860, 0xffffffff3493ba00, 0xffffffff34c00000)
Local Time = Mon Feb 12 21:49:40 2007
Elapsed Time = 61687
# The exception above was detected in native code outside the VM
# Java VM: Java HotSpot(TM) 64-Bit Server VM (1.4.2_07-b05 mixed mode)
3) A dbx on the Java core shows the location in the JNI code where the core dump occured.
dbx `which java` core
For information about new features see `help changes'
To remove this message, put `dbxenv suppress_startup_message 7.3' in your .dbxrc
Reading java
dbx: internal warning: writable memory segment 0x7cb00000[16384] of size 0 in core
core file header read successfully
Reading ld.so.1
Reading libthread.so.1
Reading libdl.so.1
Reading libc.so.1
Reading libc_psr.so.1
Reading libjvm.so
Reading libCrun.so.1
Reading libsocket.so.1
Reading libnsl.so.1
Reading libm.so.1
WARNING!!
A loadobject was found with an unexpected checksum value.
See `help core mismatch' for details, and run `proc -map'
to see what checksum values were expected and found.
dbx: warning: Some symbolic information might be incorrect.
t@1 (l@1) terminated by signal ABRT (Abort)
0xffffffff7eea822c: lwpkill+0x0008: bcc,a,pt %icc,_lwp_kill+0x18 ! 0xffffffff7eea823c
Current function is Java_getLoid (optimized)
7239 e = cod_to_long (*(o_object*) data, &loid_as_long);
(dbx) where
current thread: t@1
[1] lwpkill(0x0, 0x6, 0xffffffffffffffe6, 0x0, 0x0, 0x0), at 0xffffffff7eea822c
[2] raise(0x6, 0x0, 0xffffffff7fffad30, 0x7fbffeff00003ff6, 0x0, 0x2), at 0xffffffff7ee58a8c
[3] abort(0x0, 0xffffffff7fffae10, 0x0, 0xfffffffffffffff8, 0x0, 0xffffffff7fffae39), at 0xffffffff7ee3e3b8
[4] os::abort(0x1, 0xffffffff7e9d295c, 0xffffffff7fffaf10, 0xffffffff7e9d24a9, 0x4b007c, 0xffffffff7eb78878), at 0xffffffff7e90951c
[5] os::handle_unexpected_exception(0x10011e600, 0xa, 0xfffffffe90345704, 0xffffffff7fffbeb0, 0xffffffff7e69c6f8, 0x0), at 0xffffffff7e907e08
[6] JVM_handle_solaris_signal(0xffffffff7fffbeb0, 0xffffffff7e9d443e, 0xffffffff7fffbbd0, 0x1, 0x0, 0x1), at 0xffffffff7e69c800
[7] __sighndlr(0xa, 0xffffffff7fffbeb0, 0xffffffff7fffbbd0, 0xffffffff7e69cb9c, 0x0, 0x0), at 0xffffffff7f2188d8
---- called from signal handler with signal 10 (SIGBUS) ------
=>[8] Java_getLoid(vjEnv = ???, cls = ???, handle = ???, attr = ???) (optimized), at 0xfffffffe90345704 (line ~7239) in "j.c"
I have added checks for this function call to ensure that no invalid pointer is being sent to it which could cause a segmentation violation.
Please could someone give me some pointers on how to solve this problem, the error occurs at this point only 12 hours after running the test case..

First step is to add the option -Xcheck:jni to your java command line. It will flag common JNI errors.
If that doesn't identify the problem, then compile your jni code with debugging symbols (-g) and add the following option to the java command line when you run your test: -XX:+ShowMessageBoxOnError. When you hit the problem again, the VM will keep the process alive instead of calling abort(). Then you can use dbx to attach to the live process and should be able to get a better idea of what went wrong.

Core dump with stlport4 and string pointers

Hello,
I am porting from SGI Irix to Sun Solaris, using OS 8 and Sun Studio 8. The program we are porting is very very large. We've compiled all code, but now are getting core dumps on several of the executables. We have traced one of the core dumps to a function that deals with string manipulation/string pointers. We wrote a very simple test program that re-produces the problem.
#include <string>
#include <iostream>
void test(char* m)
std::cout << m << " in test before";
m[0] = 'z';
std::cout << m << " in test after";
void main(void)
char* temp = new char[10];
temp = "abcd";
std::cout << temp << " before test";
test(temp);
std::cout << temp << " after test";
We get the following output:
abcd before test
abcd in test before
Segmentation fault (core dumped)
The code compiles and runs fine on the SGI Irix system. What am I doing wrong?
Thanks,
Bob

1) The signature of "main" is wrong. It must be 'int
main(int, char **)'Not quite. The signatures
int main()
int main(void)
are also allowed. (C++ standard, section 3.6.1 Main function)
A "void" return type on main is not standard, but Sun C++ allows it with a warning. Such a version of main does not return a predictable value to the program that invoked it (usually the shell).
It seems as if the intent of the program is to
allocate a new string with the contents "abcd".
Instead, you allocate a buffer, and then overwrite the
pointer to that buffer with a pointer to a string
constant, to which you then attempt to write.Right. By default, the C++ compiler allocates string literals to read-only memory, to catch mistakes like this. The compiler has an option to store literal strings in read-write memory, but we recommend against using the option, since you should not ever want to modify a literal string.
I am curious why the compiler doesn't complain about
the assignment in main - to my eyes it looks like it
should be complaining that you are assigning a const
char * to a char *The compiler emits a warning about the assignment.
Such code is allowed but deprecated in the C++ standard, because of the deprecated conversion of "array of const char" to char* (section 4.2 Array-to-pointer conversion).

Getting "Baseband Core dump in progress" and after that 3G doesn't work

My iPhone 4 told me several times that there is a Baseband Core dump in progress. After that my 3G connection doesn't work anymore. Only a reboot of the iPhone solves the damaged connection.
This behavior is going to make me angry. Can someone tell me how to solve this issue?
P.S: I'm not using any beta iOS Version.

It's basically dumping a bunch of information from memory about the current state of the kernel and what not, so that it has a detailed error report to send to Apple. This data is uploaded to Apple when you sync with iTunes. Essentially an execution path of "core code". This is behavior typical of beta software, yet you state you're not running beta software on your phone...are you positive? If not, I've seen this with jailbroken phones.

Tracing speciific transactions (bus code core dump)

hi
When i am running payroll(calculation) for specific records or some employee i am getting error buse code core dumped.I am using oracle 8.1.7 and forms 4.5.I am not getting any erorrs in logs or application related.The application exiting with these error.How can i track these event.How to enable session tracing or set events.How can i trace in database level not in application level becasue this core is generating specific employee not for all.
with regards
ramya

I completed testing all the code.
First I verified that my makefile and
runtime environment were both 1.1.8.
DOMSample - ok
DOMNamespace - failed
SAXSample - failed
SAXNamespace - failed
Tokenize - ok
So - what where is it failing
I found that the parse method was failing
==parser.parse(url);
The URL was not the problem. The only
other differences in the example code is
that these flags are set -- When you add them
to DOMNamespace - THE EXAMPLE WORKS!
// Set various parser options: validation on,
// warnings shown, error stream set to stderr.
parser.setErrorStream(System.err);
parser.setValidationMode(true);
parser.showWarnings(true);

Core Dump - Code built on 2.6 and run on 2.8

Similar Messages

Maybe you are looking for