Stats

  • Locked Locked
  • Replies 4
  • Subscribers 61
  • Views 14981
  • 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

Exit Error in LEC batch mode

archive

Hi Guys,

I got one problem when I ran lec in batch mode:

$> lec -nogui -ultra -dofile mc_lec.do

In mc_lec.do file, the last command is : exit -f

But somehow, xterm pops up the following messages:

// Command: report message -compare -verbose > reports/mcv2/lec.cmpmsg
// Command: report compare data -class noneq > reports/mcv2/lec.noneq
// Command: report unmapped points -Extra -notmapped > reports/mcv2/lec.notmap
// Command: report compare data -class abort > reports/mcv2/lec.abort
// Command: exit -force
// ERROR [Internal]:
// Exit and report the error to Cadence Customer Support

and can't go back to normal tcsh mode..

And I can't use CTR^C and CTR^X to exit...

Does anyone have the same problem?

Thanks

James


Originally posted in cdnusers.org by jianyu2000
Parents

  • Hi James

    I just looked at our OS support matrix and I can't find RedHat 6.1 mentioned. The matrix starts at 4.3 (4 years ago). From 4.3 to 5.2, Red Hat support was for 7.x, 8.0, and 9.0.

    Anyway you can run on a machine with a more recent OS? Current supported is EE3.0 and RHEL4.0.

    I would also give 07.10-p100 a shot if you can.

    Chrystian


    Originally posted in cdnusers.org by croy
Reply

  • Hi James

    I just looked at our OS support matrix and I can't find RedHat 6.1 mentioned. The matrix starts at 4.3 (4 years ago). From 4.3 to 5.2, Red Hat support was for 7.x, 8.0, and 9.0.

    Anyway you can run on a machine with a more recent OS? Current supported is EE3.0 and RHEL4.0.

    I would also give 07.10-p100 a shot if you can.

    Chrystian


    Originally posted in cdnusers.org by croy
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.