Segmentation fault in BRSL DirectionalValves models
In some models of our BRSL models ocuring segmantion faults.
e.g. for the model Rexroth_Generic_Test.Hydraulics.DirectionalValves.DirectionalValve32_Easy_TC01
the gdb back trace is:
Thread 1 received signal SIGSEGV, Segmentation fault.
0x0000000000722256 in indexed_assign_real_array ()
(gdb) bt
#0 0x0000000000722256 in indexed_assign_real_array ()
#1 0x0000000000416b64 in omc_Rexroth__Generic_Hydraulics_Valves_Internal_calcFlowTable ()
#2 0x000000000047a672 in Rexroth_Generic_Test_Hydraulics_DirectionalValves_DirectionalValve32_Easy_TC01_eqFunction_1311 ()
#3 0x0000000000474267 in Rexroth_Generic_Test_Hydraulics_DirectionalValves_DirectionalValve32_Easy_TC01_updateBoundParameters_0 ()
#4 0x000000000046f351 in Rexroth_Generic_Test_Hydraulics_DirectionalValves_DirectionalValve32_Easy_TC01_updateBoundParameters ()
#5 0x000000000076122d in initialization ()
#6 0x000000000073f846 in initializeModel ()
#7 0x0000000000740b38 in solver_main ()
#8 0x0000000000765f6b in callSolver(DATA*, threadData_s*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, double, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, int, char const*) ()
#9 0x0000000000765065 in startNonInteractiveSimulation ()
#10 0x000000000076878f in _main_SimulationRuntime ()
#11 0x000000000041632e in main ()
Change History
(5)
Cc: |
Sven.Baetzing@… added
|
Summary: |
Segmantation fauls in BRSL DirectionalValves models → Segmantation faults in BRSL DirectionalValves models
|
Milestone: |
NeedsInput → 1.17.1
|
Owner: |
changed from Andreas Heuermann to Adrian Pop
|
Status: |
new → accepted
|
Milestone: |
1.17.1 → 1.18.0
|
Resolution: |
→ fixed
|
Status: |
accepted → closed
|
Summary: |
Segmantation faults in BRSL DirectionalValves models → Segmentation fault in BRSL DirectionalValves models
|
@niklwors reports that his colleagues found this problem is solved on 1.18.0-dev. We may try to figure out what fixed that if we really need 1.17.1 as a backup option, in case something goes wrong with 1.18.0.
@niklwors, @adrpo, please double-check and reopen, in case it's not fixed yet on master.