What to do when ocean input gets stuck?

Discussion in 'Cadence' started by Svenn Are Bjerkem, Jan 12, 2005.

  1. Hi,
    when doing some typing on the ocean command line, I got into something
    that I obviously don't get out of. I get no feedback just new linefeeds,
    and ctrl-c give me back the prompt with an error message
    *Error* parser: interrupted while reading input.
    I can't use ctrl-z to background it to kill it.

    Is there some magic way to end the command line input parsing, or do I
    have to kill the window and start a new one?
     
    Svenn Are Bjerkem, Jan 12, 2005
    #1
  2. I've seen this happen with the ocean executable sometimes. Unfortunately
    because of the way that the interface is implemented, this kind of thing
    happens. Also it annoys me that trace output is swallowed in the ocean
    executable...

    I think it's a consequence of how the GUI is replaced by a textual input,
    whilst still keeping the GUI behind the scenes.

    Probably should log a service request for it, although I'm sure it's hard to
    reproduce...

    Andrew.
     
    Andrew Beckett, Jan 24, 2005
    #2
Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.