Stats

  • Locked Locked
  • Replies 4
  • Subscribers 125
  • Views 14510
  • 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

Assura QRC error in batch mode.

MedAn

Hi all!

Could you pls. help me to resolve some issue.

When I start Assura QRC form layout view - all works fine, but when I try to start the same in the batch mode,  I have following error:

SAVEDIR=`beginFlattenInputs`
beginFlattenInputs
export SAVEDIR
/bin/mv -f NET h_NET
flatnet -V -li -h '/' h_NET NET
Usage so far 0.00 user, 0.00 sys, 0.00 elapsed, 100284.0 kbytes
run out of memory or swap space for malloc(): Cannot allocate memory
ERROR (LBMISC-215023): run out of memory or swap space for malloc(): 0 bytes asked

ERROR (LBRCXM-609): Bad return status from RCX run. 0xff00

INFO (LBRCXM-709): ***** Quantus QRC terminated abnormally *****

Virtuoso version is: sub-version  IC6.1.7-64b.500.7 

QRC version is: 14.2.2-s209

Parents
  • Andrew Beckett

    I'm not sure how it can be different since the UI simply calls qrc in batch mode. The only thing I can think of is that you are accidentally running QRC in 32-bit mode when running from the command line? That should be apparent from the log file (you included so little above that I cannot tell).

    Also, why are you using such an old version of Quantus QRC? No need to use a version from 4-5 years ago...

    Andrew.

  • MedAn
    in reply to Andrew Beckett

    I'm using ccl file which was generated by cadence and simple try repeat it in the same environment: qrc -cmd <path_to_the_ccl_file> > myLog.log

    in head of the log file I have:

    Cadence Quantus QRC Etraction - 64-bit Parasitic Extractor - Version 14.2.2-s209 Tue Mar 24 21:31:22 PDT 2015.

    If it needed, I can attach the log file.

    Ok, I will try to use another version, which version you recommend?

  • Andrew Beckett
    in reply to MedAn

    In that case, I'm not sure what it is. The message says it failed to allocate memory - unclear why that should be any different with the 64-bit extractor from the command line than from the UI.

    I would suggest trying with the latest EXT182 hotfix or maybe EXT191 which is now released. If that doesn't work, please contact customer support as we're likely to need to see the testcase that has the problem.

    Regards,

    Andrew.

Reply
  • Andrew Beckett
    in reply to MedAn

    In that case, I'm not sure what it is. The message says it failed to allocate memory - unclear why that should be any different with the 64-bit extractor from the command line than from the UI.

    I would suggest trying with the latest EXT182 hotfix or maybe EXT191 which is now released. If that doesn't work, please contact customer support as we're likely to need to see the testcase that has the problem.

    Regards,

    Andrew.

Children
  • MedAn
    in reply to Andrew Beckett

    Thx. to you Andrew, when I changed version on 17.1.1-s059 the problem has gone. 

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.