![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: -R-E- DXL: <Line:0> Stack Underflow Topic Summary: Error when adding one more variable Created On: 12-Aug-2005 08:22 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
If I add one more variable (int, bool, string) to my allready running DXL script I get the message: |
|
![]() |
|
![]() |
|
Can you post the script? We might then stand a chance of getting to the root of your problem...
------------------------- Paul dot Tiplady at TRW dot com TRW Automotive |
|
![]() |
|
![]() |
|
Hi,
i got the same problem. Just a bit different. If a do NOT add a array (no matter if at the beginning or at the end of the script) i get this stack underflow.
That is so strange.
Stefan
------------------------- Stefan dot Ruehle at TRW dot com TRW Automotive Radolfzell/Germany |
|
![]() |
|
![]() |
|
Look in help file for: pragma stack
|
|
![]() |
|
![]() |
|
Now i found where the trouble is. I create a partition definition and want to dispose it afterwards. Without the disposal i have no error but with the disposal active i have to declare an empty array otherwise i get the "stack underflow".
Looks like a memory-leak to me...
Help is appreciated.
Stefan
------------------------- Stefan dot Ruehle at TRW dot com TRW Automotive Radolfzell/Germany |
|
![]() |
|
![]() |
|
Pragma stack doesn't help.
It seems that the error is caused by "dispose PartitionDefinition". Without this command there is no problem. With it i have to define an empty array. How can this be?
------------------------- Stefan dot Ruehle at TRW dot com TRW Automotive Radolfzell/Germany |
|
![]() |
|
![]() |
|
An old thread topic but keeps returning. I have a DXL that simply dumps metrics from a specific module to a 2kb TSV file. When run from DXL Editor it works fine. When run from a DOORS shortcut using a command string like:
-D "#include <C:/path/metrics.dxl>" it gets the infamous Stack Underflow at line 0 error, complete with a diagnostic log window and the also-infamous "unexpected internal error, suggest save, exit and restart". In case it matters, the DXL does declare and initialize several 1-dimensional arrays. Any advice? Thx Tom |
|
![]() |
|
![]() |
|
Enclose the entire script in braces and try again.
------------------------- Tony Goodman http://www.smartdxl.com |
|
![]() |
|
![]() |
|
I also have had huge problems with Arrays. I was constantly getting errors and crashes when simply putting values into an array(was statically declared not dynamic) and trying to read them out. If I took the Array initialization and extraction code out and ran it separately it worked fine but inside the script it didn't work. I wasn't touching the Array prior to using it. I ended up just using a string[] array.
------------------------- David Pechacek AAI Services Textron dpechacek@sc-aaicorp.com David.Pechacek@gmail.com |
|
![]() |
|
![]() |
|
Thanks Tony! Worked like a charm. Why didn't *I* think of enclosing the entire script in braces! For extra credit, can you explain why that solved this problem?
Tom |
|
![]() |
|
![]() |
|
When you run a script in client mode the interpreter automatically encloses the script in braces. This ensures thatthe script is running in it's own context. This explains why you can #include files that are already #included in the top context without any clashes. It also explains why you can overload variable names that exist globally.
However, when you run the same script in batch mode it doies not get wrapped in braces and you can get name clashes etc. ------------------------- Tony Goodman http://www.smartdxl.com |
|
![]() |
Telelogic DOORS
» DXL Exchange
»
-R-E- DXL: <Line:0> Stack Underflow
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.