• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Custom IC SKILL
  3. How to let the messages not show in shell terminal when...

Stats

  • Locked Locked
  • Replies 5
  • Subscribers 143
  • Views 14160
  • 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

How to let the messages not show in shell terminal when use ipcBeginProcess ?

Charley Chen
Charley Chen over 11 years ago

Hello All,

I use  ipcBeginProcess to do something , but I don't want the messages show in xterm , 

How to do it ?

 

Thank you,

Charley 

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 11 years ago

    Charley,

    If you're using ipcBeginProcess, then either you can use the "asynchronous" form and provide functions to consume the stdout and stderr output, or you can use the synchronous apprach and use ipcReadProcess. Output shouldn't appear in the xterm, since both stdout and stderr get sent to Virtuoso.

    So I don't understand your problem.

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Charley Chen
    Charley Chen over 11 years ago

    Hi Andrew,

    I use  ipcId = ipcBeginprocess("strmin ..."  nil dataHandle errorHandle log) , 

    I see the message sent to the xterm . 

     

    Thank you,

    Charley 

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Charley Chen
    Charley Chen over 11 years ago

    Hi Andrew , 

    I found the problem and know how to solve  it. , it's the log file  is used , it will sent message to xterm .

     If I use  ipcId = ipcBeginprocess("strmin ..."  nil dataHandle errorHandle log) ,  it will sent message to xterm

    If I use  ipcId = ipcBeginprocess("strmin ..."  nil dataHandle errorHandle ) ,  it won't sent message to xterm

     

    Thank you,

    Charley 

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 11 years ago

    Charley,

    Presumably you didn't actually use those calls, because the function has a capital P  in Process, the second argument should be a string (e.g. "") rather than nil, and the log file name is the 6th argument, not the 5th (the 5th is an exit handler).

    If I use:

    procedure(MyDisplayStuff(cid data) printf("STUFF: %L\n" data))
    procedure(MyExitHandler(cid status) printf("EXITED: %L\n" status))
    ipcBeginProcess("/bin/ls" "" 'MyDisplayStuff 'MyDisplayStuff 'MyExitHandler "log")

    Then I get nothing in the terminal, but I do get a file called log. If the file "log" is not writable for some reason, I get this in the xterm:

      Server: could not open/create logfile log

    Is that what you mean?

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Charley Chen
    Charley Chen over 11 years ago

    Andrew , 

    Thank you for correct me the usage and explain it.

    Charley 

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information