• 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 does abeMTdebug work?

Stats

  • Locked Locked
  • Replies 0
  • Subscribers 143
  • Views 6222
  • 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 does abeMTdebug work?

SteveAvery
SteveAvery over 2 years ago

I'm trying to debug some ABE code that is going awry, and can't work out how abeMTdebug is supposed to work.

The documentation says: "Enables the output of additional messages to monitor progress when multithreading is used" but doesn't explain where those additional messages go. There do not seem to be any additional messages in CDS.log or the CIW, and running the code from within the SKILL IDE doesn't seem to result in any extra information being displayed.

This snippet of code is representative of what I'm doing:

(setq obstruction_layer (abeNewLayer))
(abeMTdebug obstruction_layer)
(foreach layer sizing_queue
  (unless (zerop (get layer "numTiles"))
    (abeLayerOr layer obstruction_layer ?queue t)))
(abeRunQueue)


sizing_queue is a list of ABE layers (the result of abeLayerSize). It is created by cons'ing layers onto sizing_queue as they're created (I have confirmed sizing_queue is a valid list of ABE layers). Layers are only added to sizing_queue if their numTiles is non-zero (ie. they all have some shapes in them - the check of numTiles in the code snippet isn't actually necessary). I do confirm that abeMTdebug returns t. 
I'm running virtuoso from ICADVM20.1-64b.500.29.

Any hints on how I should be making use of abeMTdebug would be greatly appreciated, as would any other hints on how to debug multithreaded ABE code.

thanks.

  • 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