![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Skip List causing DXL runtime error w/o error line Topic Summary: Skiplist of modules is run through, but no error line given when script exits at runtime Created On: 18-Nov-2005 00:31 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() Answer: Thanks for the feedback Reik! I re-implemented my whole script replacing the skiplists with arrays and even input files, but nothing worked. However, just minutes ago I found the solution. Apparently, DOORS will only run so many iterations of any combinations of loops, after which point it simply exits (as we saw in my script). To get around this, I simply added this one line: pragma runLim, 2500000 Now it's all fixed! Jason | |
![]() |
|
|
|
![]() |
|
![]() |
|
Hi Jason,
I had a look into your code and found only some little things. May be, you should declare lastMod as Date ?! I'm not really sure, how the autodeclare mechanism in DOORs is working ![]() And in main function you loop through mySkipList and then use (string key srs_modules) --> usually this should run into an error (use of key function outside loop ?!). May be that helps to solve your problem, greetings Reik ------------------------- Evosoft GmbH for Siemens Industry Sector Berlin, Germany |
|
![]() |
|
![]() |
|
Thanks for the feedback Reik!
I re-implemented my whole script replacing the skiplists with arrays and even input files, but nothing worked. However, just minutes ago I found the solution. Apparently, DOORS will only run so many iterations of any combinations of loops, after which point it simply exits (as we saw in my script). To get around this, I simply added this one line: pragma runLim, 2500000 Now it's all fixed! Jason Edited: 22-Nov-2005 at 23:19 by jason haury |
|
![]() |
|
![]() |
|
Thanks for posting the solution Jason, I had tried to replicate your problem but without success.
|
|
![]() |
|
![]() |
|
When running normally you'd get a DXL timeout dialog, offering to cancel, continue, or continue doubling the timeout. Batch mode offers no such user interaction so it ends.
Production code should perhaps have "pragma runLim, 0" which means no timeout, although while debugging you may want a time out to help find infinite loop bugs. - Louie |
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.