#3448 closed defect (fixed)
Stack Overflow Detected in OMEdit
Reported by: | Adam Dershowitz | Owned by: | Martin Sjölund |
---|---|---|---|
Priority: | high | Milestone: | 1.9.4 |
Component: | Frontend | Version: | trunk |
Keywords: | Cc: |
Description
If I try to run Modelica.Fluid.Examples.BranchingDynamicPipes in OMEdit I get the following:
[1] 11:20:08 Scripting Notification Stack overflow detected and was not caught. Send us a bug report at https://trac.openmodelica.org/OpenModelica/newticket Include the following trace: [bt] Execution path:
and nothing else happens (progress window doesn't open etc). I am running 1.9.4~dev that I just built, on a Mac, and a number of other models all seem to build and run correctly.
According to the recursive BuildModel Test page, this is a model that should be working currently. I see that there were a few recent changesets related to catching stack overflows. So, that probably relates.
Change History (8)
comment:1 by , 9 years ago
comment:2 by , 9 years ago
Seems to be a stack overflow in: omc_NFSCodeDependency_collectUsedElements2.
I will improve the stack overflow detection for OSX (sadly, it will be missing in 1.9.3).
comment:3 by , 9 years ago
Stack overflow detected and was not caught. Send us a bug report at https://trac.openmodelica.org/OpenModelica/newticket Include the following trace: [bt] #1 libOpenModelicaRuntimeC.dylib(mmc_setStacktraceMessages_threadData) [bt] #2 libOpenModelicaCompiler.dylib(NFSCodeDependency.collectUsedElement) [bt] #3...1024 libOpenModelicaCompiler.dylib(NFSCodeDependency.collectUsedElements2) [bt] #1025 [...]
comment:4 by , 9 years ago
Component: | Unknown → Frontend |
---|---|
Milestone: | Future → 1.9.4 |
Owner: | changed from | to
Status: | new → accepted |
comment:5 by , 9 years ago
Resolution: | → fixed |
---|---|
Status: | accepted → closed |
I now fixed the stack overflow. It didn't crash OMEdit before, right? Just printed that message? Otherwise, there are more changes necessary.
comment:6 by , 9 years ago
Yes, it didn't crash before, and yes it now seems to be fixed.
Thank you.
I just downloaded the nightly 1.9.3 VM Linux image, and when I try it there it does run correctly.