Stats

  • Locked Locked
  • Replies 1
  • Subscribers 143
  • Views 13441
  • 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

automatic stack strace for errors.

LDIL

Hello all. Let's say that I run this code snippet:

procedure( ko(i ) bar( i*2 ) ) procedure( bar( j ) printf( "yo %d\n" ) ) ko( 2.3 )

I get:


*Error* fprintf/sprintf: too many format specs.

However, I need to look and see which procedure was calling  printf.

One could surround snippets of the code with error handling, and then issue an error, but this is, well, rather cumbersome.

I assume that some macro can be

Is there a way to have the stack-trace printed automatically when such error is issued, and/or get the line in the procedure which caused it, or number of step (in this case, 1, or 0, which number one wants to start counting).

Thanks,

  • Andrew Beckett

    If you set this variable:

    _stacktrace=50

    Then you'll get a stack trace displayed when there is any error. Alternatively, if you have the SKILL Debugger enabled you can also choose to see local variables, the stack trace - most easily done through the SKILL IDE. It will even highlight the line in the code where the error occurred.

    Andrew.

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.