Intel® Quartus® Prime Software
Intel® Quartus® Prime Design Software, Design Entry, Synthesis, Simulation, Verification, Timing Analysis, System Design (Platform Designer, formerly Qsys)
17049 Discussions

ModelSim Looping in vish.exe

Altera_Forum
Honored Contributor II
‎07-21-2009 06:07 PM
2,874 Views

Quite frequently while stopped at a breakpoint during a VHDL functional simulation, ModelSim Starter Edition 6.4a will become non-responsive. The hourglass icon is displayed. Simulation time is not being updated, so I don't believe it is actually simulating. I have not requested continued simulation nor any stepping. I may have left-clicked on some part of the displayed source. The menu bar (File Edit View...) is blank! 

 

Windows XP PRO SP2 

 

vish.exe is utilizing 100% of the CPU and nothing happens forever. Must use task manager to kill vish.exe 

 

Any idea what causes this and how to avoid it?
0 Kudos

Link Copied

1 Reply
Altera_Forum
Honored Contributor II
‎02-18-2011 07:40 PM
2,026 Views

I have the same problem with ModelSim Starter Edition 6.5b running on Linux. 

I found a text with google that said that ModelSim had some problem to have several instances of ModelSim installed. I guess that they meant that there could be problem to run several instances of any version at the same time. That would explain this problem... 

But I don't know why and I would really like to get around the problem. 

Anyone that have an idea?
0 Kudos
Copy link
Reply

Community support is provided Monday to Friday. Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.