libjsig.so

[Christian Meier]

Hi

We use "export LD_PRELOAD=<libjvm.so dir>/libjsig.so" in our application.
And everything was doing right in the old 32-bit system. Now we have our
application running in a 64 system and now we have a segmentation fault. It
doesn't work neither when we link it directly in our application...
We could reduce our problem and we are sure that it is independent of our
application.
"java -version" ends in a core dump when using "export LD_PRELOAD=<libjvm.so
dir>/libjsig.so".
We are using a sun solaris and Java(TM) 2 Runtime Environment, Standard
Edition (build 1.4.2_03-b02), Java HotSpot(TM) 64-Bit Server VM (build
1.4.2_03-b02, mixed mode).....
Can anyone help me? Or is there anyone who had the same problem? Do you have
some ideas?
Thanks for every kind of help!

Greetings Chris

[sf]

Hi Christian,

.... so you are using the v1.4.2 signal chaining library...

http://java.sun.com/j2se/1.4.2/docs/...-chaining.html

Do you have any more details from the SEGV?

Do you have a core file?

Do you get the same SEGV if you run in "client" compiler
or in '-Xint'interpreted mode execution only?

Tell us more...

Thanks,

Stephen
Christian Meier wrote:

Hi

We use "export LD_PRELOAD=<libjvm.so dir>/libjsig.so" in our application.
And everything was doing right in the old 32-bit system. Now we have our
application running in a 64 system and now we have a segmentation fault. It
doesn't work neither when we link it directly in our application...
We could reduce our problem and we are sure that it is independent of our
application.
"java -version" ends in a core dump when using "export LD_PRELOAD=<libjvm.so
dir>/libjsig.so".
We are using a sun solaris and Java(TM) 2 Runtime Environment, Standard
Edition (build 1.4.2_03-b02), Java HotSpot(TM) 64-Bit Server VM (build
1.4.2_03-b02, mixed mode).....
Can anyone help me? Or is there anyone who had the same problem? Do you have
some ideas?
Thanks for every kind of help!

Greetings Chris

[Roedy Green]

On Fri, 16 Apr 2004 16:29:21 +0200, "Christian Meier" <ch***@gmx.ch>
wrote or quoted :

in our application.
And everything was doing right in the old 32-bit system. Now we have our
application running in a 64 system and now we have a segmentation fault

I am not lucky enough to have either sort of server in my office, so
will have to make a wild stab. When you say native to the 64-bit JVM
perhaps it expects only 64-bit code to be linked, and just lies on its
side if you give it 32-bit code.

Do you have a way of generating 64 bit JNI code?

--
Canadian Mind Products, Roedy Green.
Coaching, problem solving, economical contract programming.
See http://mindprod.com/jgloss/jgloss.html for The Java Glossary.

[Christian Meier]

Hi

First, thanks for your help!
No, I have no more details from the SEGV. I just enter in the bash
"java -version" ond get "Segmentation Fault (core dumped)".
Yes, I have a core file, but its whole size is 1305 KB.... I don't know, if
I can post it here in the newsgroup. Shall I? I suppose there is not much
readable information in the file.
With -Xint option I have the same problem. There is also a segmentation
Fault.
I found out that there are different versions of libjsig.so. Is it possible
that it works if I will use the libjsig.so of version 1.4.0? Can there be
some other "not-wanted features"?

Thanks and greets
Chris
"sf" <my******@yahoo.com> schrieb im Newsbeitrag
news:40**************@yahoo.com...

Hi Christian,

... so you are using the v1.4.2 signal chaining library...

http://java.sun.com/j2se/1.4.2/docs/...-chaining.html

Do you have any more details from the SEGV?

Do you have a core file?

Do you get the same SEGV if you run in "client" compiler
or in '-Xint'interpreted mode execution only?

Tell us more...

Thanks,

Stephen
Christian Meier wrote:

Hi

We use "export LD_PRELOAD=<libjvm.so dir>/libjsig.so" in our application. And everything was doing right in the old 32-bit system. Now we have our
application running in a 64 system and now we have a segmentation fault. It doesn't work neither when we link it directly in our application...
We could reduce our problem and we are sure that it is independent of our application.
"java -version" ends in a core dump when using "export LD_PRELOAD=<libjvm.so dir>/libjsig.so".
We are using a sun solaris and Java(TM) 2 Runtime Environment, Standard
Edition (build 1.4.2_03-b02), Java HotSpot(TM) 64-Bit Server VM (build
1.4.2_03-b02, mixed mode).....
Can anyone help me? Or is there anyone who had the same problem? Do you have some ideas?
Thanks for every kind of help!

Greetings Chris

[Lucas Bergman]

Christian Meier <ch***@gmx.ch> wrote:

No, I have no more details from the SEGV. I just enter in the bash
"java -version" ond get "Segmentation Fault (core dumped)". Yes, I
have a core file, but its whole size is 1305 KB.... I don't know, if
I can post it here in the newsgroup. Shall I?

No. Unix core files are only useful in the context of the exact
kernel, executables, libraries, etc. involved in generating them.
Don't ever send someone else a core file unless you intend to send
him/her your computer as well.

You could try to get a backtrace out of the core file (which would
make sense to the developers) if your library and/or program contain
symbol information. See, for example:

http://www.sys-con.com/story/?storyid=44022&DE=1

-- Lucas