Open fred777 opened 8 years ago
Do you have the hs_err_pidXXXX file from the crash? Probably in the working directory?
There is none I'm afraid. I guess the crash happens right within the /bin/wrapper binary, JVM does not get fired up before the crash.
But I don't have access to the machine before Monday. I'll try to get a stack trace.
Maybe it's an issue with Raspberry PI B instruction set, which is different from Raspberry PI2.
I tried pi-server on a different machine (no Raspberry, but comparable to PI2, i.e. ARMv7, and there was no segfault or crash)
I upgraded JSW in the 1.1.0 release... and it's possible that in prior versions I was using a custom-compiled version of JSW in order to gain ARMv6 compatibility (some Googling leads me to believe this is, or at least used to be, necessary). I know I did that at one point, I just don't remember releasing with it! If that's the case I'm not quite sure how to proceed yet.
I used to be using a Pi 1 B or B+, and now I'm using a Pi 2 B, so of course it works for me now... because the Pi 2 is ARMv7.
Ok, so there is no easy fix... But never mind - I just wanted something to try out opcua out-of-the-box without much coding and invoking the server via
cd lib
sudo java -cp .:* com.digitalpetri.opcua.raspberrypi.PiServer
is sufficient.
Hi Kevin,
I just tried the pi-server (released 1.1.0-zip file) on a Raspberry PI B (without +) and it segfaults in wrapper binary.
I don't have a clue why. It's not related to gpio config. It doesn't get to that point.
The PI is running raspbian jessie and Openjava JRE 8 headless.
GDB says, segfault happens in 0x0005a6fe in queueMessages ()