Assura terminates on Segmentation violation

Hi,

I am running Assura on a digital design with memories.
My run terminated with the following error, as described below.

I have checked the machine's memory and spaces, they are more than
sufficient.

Thanks a lot.

Regards,
Dinac.


**********************************************************************************

Assura (tm) Physical Verification Version
av3.1roduction:dfII6.1.2-64b:
Release 3.1.7_USR2
......
.....
...
....
Top cell 'base' specified, starting from specified point...
Preprocessing schematic network phase 1
Preprocessing layout network phase 1
Preprocessing schematic network phase 2
Preprocessing layout network phase 2
cpu=0.11m wall=0.12m mem=150.64mb

Finished /cadence/assuraoa317/tools/assura/bin/nvn

Executing: bulk = cellBoundary(root)

Executing: data = cellBoundary(root)

Abnormal termination at Tue Nov 17 18:25:52 2009
intermediate: 15.92dt 1090dw 15.98t 965.5meg -47pf 0.0rss -20816r
20272w
errno: 0, code: 1

*ERROR* Segmentation violation - run abnormally terminated

*WARNING* Bad exit from child process .. 0x100


***** aveng terminated abnormally *****


*WARNING* aveng exit with bad status
*WARNING* Status 256
*WARNING* Assura execution terminated


***** aveng fork terminated abnormally *****

 

Hi Dinac,

What about Assura ? did you run Assura in 64 bits mode ?

Cheers,
Riad.

 

Hi Riad,

Thanks a lot for your mail and it strike me a hint.
I have to run in assura 32 bit, previously I had some similar issue
and had to change to 32 bit to run assura successfully. I think this
version has some problem with 64bit.

I will run it in 32 and check it.

Thanks
Dinac

 

Hi ,

Assura did run in 32bit. But it again terminated with not enough
memory.
Is there a way to solve this or a way to allocate enough memory. I
guess it is the virtual memory.

Thanks Again,

cheers
Dinac


************************************************************************************
Assura (tm) Physical Verification Version
av3.1roduction:dfII6.1.2:IC6.1.2.149
Release 3.1.7_USR2

Copyright (c) Cadence Design Systems. All rights reserved.
@(#)$CDS: assura version av3.1roduction:dfII6.1.2:IC6.1.2.149
02/29/2008 05:15 (dfm30ee01) $
sub-version 3.1.7_USR2, integ signature 2008-02-29-0423

....
...

elapsed time = 2.57 minutes, cpu time = 2.55 minutes

Executing: widthMOS = measureParameter(length (gateLayer butting
diffLayer) 0.5)
elapsed time = 28.00 seconds, cpu time = 26.04 seconds

Executing: areaMOS = measureParameter(area (gateLayer))
ERROR: Memory used 2957 MB, out of memory (swap space)
ERROR: Memory used 2957 MB, out of memory (swap space)
ERROR: Memory used 2957 MB, out of memory (swap space)
ERROR: Memory used 2957 MB, out of memory (swap space)


Currently generating layer 1488/2256 in cell 'base layout
x1' (950/2367) at level 0
*ERROR* Out of virtual memory (swap space) - run terminated

ERROR: Memory used 2957 MB, out of memory (swap space)
Insufficient memory to continue.
Cannot satisfy request for 1073741808 more bytes of memory.
Terminating process.

*WARNING* aveng exit with bad status
*WARNING* Status 256
*WARNING* Assura execution terminated


***** aveng fork terminated abnormally *****

 

dinac wrote, on 11/24/09 11:34:

I would first suggest trying a more recent Assura version (in 64 bit mode), such
as the latest Assura 4.1 version. 3.1.7 is a little old (there has been 3.2 and
4.1 since then). If it still fails, you should contact Cadence customer support.

Regards,

Andrew.

 

thanks Andrew
You are right, with the later version Assura completed the run.

Thanks again,

cheers
Dinac