Stats

  • Locked Locked
  • Replies 2
  • Subscribers 125
  • Views 13830
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Colormap overflow, SIGFPE and floating exception

Grover

Ealier today, Virtuoso 6.1.3 crashed with a Bus Error, and since then it seems that the design I was working on has become corrupt in some way. When I load the adexl setup of my cell and simulate, the CIW says "*Error* SIGFPE caught: possibly caused by (integer) divide-by-zero", aborts the simulation and plots the results from a previous run. If I then press "Simulate" again, the whole program dies with a Floating exception.

When I load another cell (not the one I was using when Virtuoso crashed), it shows this in the simulation job log:

\w *WARNING* (LAYERS-101225): X-Colormap overflow.
\w *WARNING* (LAYERS-101226): Colors snaorange, snagold, snayellow, snalime, snabluegreen, snacadetblue, and snasalmon are not defined.
\o (LAYERS-101002): Please exit some applications to free color cells from X-Colormap
\o (LAYERS-101003): or increase layer pool size by "setenv CDS_LAYER_POOL_SIZE n".

And while this cell does simulate correctly, the traces in ViVa appear in totally different colours after every simulation run. This is confusing, and not like it was before.

I tried deleting my .cdsenv, and setting up a new adexl view for the circuit that's crashing, but to no avail. Could it be that the cell has become damaged somehow? Or is there something wrong with a configuration file, causing the Colormap error? Does anyone know what's gone wrong today?

Parents

  • I've contacted Customer Support, and after a while I finally found out what went wrong: someone applied the latest Hotfix (6.1.3.500.13) without telling me, and this caused Virtuoso to crash when using an old simulator state. The colour replacement problem was caused by one of the scripts in the design kit I'm using, which doesn't work correctly with this new Hotfix.

    Moral of the story: thoroughly test any new Hotfixes before applying them to an environment that others are using...

Reply

  • I've contacted Customer Support, and after a while I finally found out what went wrong: someone applied the latest Hotfix (6.1.3.500.13) without telling me, and this caused Virtuoso to crash when using an old simulator state. The colour replacement problem was caused by one of the scripts in the design kit I'm using, which doesn't work correctly with this new Hotfix.

    Moral of the story: thoroughly test any new Hotfixes before applying them to an environment that others are using...

Children
No Data

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.