Closed bberak closed 3 years ago
The clue in that stacktrace is the failure of Computation::InitNETFrameworks(), which is trying to load the Cotton dll.
Did the cotton dll build properly? It has a weird password requirement that you'll have to ask @hol353 for.
Thanks @peter-devoil - nice find.
Yes, the Cotton.dll did build - the BuildAll.sh command runs and completes successfully. I found the password for the Cotton.dll build buried somewhere in the SVN artefacts.
OK, so cotton is the first .NET component it's trying to load, and it doesnt look like it's even got to call the initialisation routine within the component.
Did the standard example cotton simulation run? If the person who gave you the sim file has given you an old-style .sim file, then much weirdness will happen during initialisation - incomplete constructors etc..
I'd suggest you update your mono to 4.8. (5.x seems to have minor troubles with apsim's vb components, and scalability in HPC environments.)
If the problem persists, I'd look at strace output. Then valgrind. But if you get there, you're in a bad place.
Thanks @peter-devoil
I'll try run the standard cotton example and see how it goes. I used ApsimToSim.exe to extract the .sim file first (for debugging purposes). The .sim file runs without error on Windows.
I'll try update to mono 4.8. Thanks a lot for your pointers!
Just remember that sim files made under windows will be different than those made under linux - the native components are called ".so" cf ".dll" on windows.
@bberak how did you go? I also have a similar issue, using 7.10-4215 and 7.10-4194. I can successfully run other apsim files, but when I try to run the example cotton files (or indeed even my own cotton apsims), I get the same output as you, including the suspect cotton.dll except with no stack trace or anything. Should I expect it to use the .dll under mono with linux? All of the other components are .so, and as a result I am a bit suss.
I ran strace
, but when I grep for cotton
in the output, I dont see it at all. Bit stumped. Any tips for chasing this down?
The .NET dlls have dll extensions - indeed the same dlls compiled under windows will also run on linux.
Did you come across this issue?
I will give this a go. I get nothing below and including Native stacktrace:
from OPs log, so unsure if its the same, but I'll give it a try
Sorry @tdonovic but I was pulled into another project shortly after I posted this question. I suspect that the problem I encountered was due to the .sim files being created under Windows (as @peter-devoil pointed out).
This issue has been automatically marked as stale because it has not had any activity in the last 30 days. It will be closed in one week if no further activity occurs. Thank you for your contributions.
This issue is being closed because there has been no recent activity. Feel free to re-open or open a new issue if needed.
Hi there,
First of all, huge thanks for creating and maintinaing this software.
I'm getting a SIGSEGV error when running a .sim file in an Ubuntu container with APSIM 7.10 (revision 4191).
I've gotten the source code to successfully compile using BuildAll.sh. I can also successfully run the .apsim files in the Examples folder.
SIGSEGV Error
However, when running a particular .sim file (given to me by a client):
I get the following error:
I've followed a combination of your linux documentation and your Dockerfile to get my container working correctly and compiling the latest source code (revision 4191).
I've prepended the following lines to ~/.bashrc:
I've also tried (to no avail):
Envrionment
OS: Ubuntu 16.04
Repository: http://apsrunet.apsim.info/svn/apsim/trunk@4191
Mono:
Any help would be greatly appreciated and please let me know if I can provide any more info!
Kind Regards!