• 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 Design
  3. cadence gdb command 'gdb' is not found or is invalid

Stats

  • Locked Locked
  • Replies 8
  • Subscribers 126
  • Views 5558
  • 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

cadence gdb command 'gdb' is not found or is invalid

matangk2
matangk2 over 2 years ago

Hi,

As per our educational contact advise, we installed Cadence IC618 on an RHEL 8 machine. I followed all instructions that i've found. Cadnce loads fine besides a single warning:

'cadence gdb command 'gdb' is not found or is invalid'

gdb is installed, so unsure what would cause the problem

will appreciate the assistance.

Best,

Matan

  • Cancel
  • matangk2
    matangk2 over 2 years ago

    Of course, I have tried, as recommended, to define env. variable 'GDB', 'DEBUGGER' or 'CDS_DEBUGGER' as 'gdb' or its actual location 'usr/bin/gdb' but to no avail.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 2 years ago in reply to matangk2

    Which IC6.1.8 sub-version have you installed? What does "virtuoso -W" return in the terminal window.

    Note that officially IC6.1.8 is not supported on RHEL8, although fixes have been made in later hotfix versions to support it.

    Finally, what is the exact error message you get? I think it's more likely to be something like this (if it's a recent hotfix you're using):

    WARNING* (PerfDiag): The GDB command '/usr/bin/gdb' is not found or is invalid.

    (not "cadence gdb command"). If it's the above, then the only downside is that the performance diagnostics won't be available should you need it.

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • matangk2
    matangk2 over 2 years ago in reply to Andrew Beckett

    Hi Andrew,

    Thanks for the prompt reply, for some reason answer does not update on my mailbox though marked the option.

    (1) Cadence version:

    'sub-version  IC6.1.8-64b.500.27 '

    (2) Well, I was told specifically (no names) by your guys that EL8 is 'definitely supported' after I raised the issue that your support doc states it's not... No matter. We'll be early adopters.

    (3) The exact error message is (first two lines in yellow)

    *WARNING* (PerfDiag): The GDB command 'gdb' is not found or is invalid.
    *WARNING* (PerfDiag): The GDB-related functionality has been disabled. Use the 'gdbPath' environment variable to set a valid GDB path or set one of the SHELL environment variables CDS_DEBUGGER, DEBUGGER, or GDB, and restart Virtuoso.
    Performance Diagnostic tool is installed. You can access PerfDiag from CIW Tools or use the shell command 'cdsPerfDiag -p 284214' to open it when Virtuoso freezes.

    (4) If I define env. variable GDB to '/usr/bin/gdb' then I get the warning as you wrote it (though gdb is there as far as I can say).

    (5) As suggested in the exact warning I attached, I can run PrefDiag from shell using the "shell command 'cdsPerfDiag -p 284214' to open it"

    It looks like functionality is still there if I wish to launch PrefDiag from command line should Cadence crash. Can you please verify that this is just a cosmetic issue? If there's a solution to warnings popping up (I don't like warnings on CIW) - great. If not, also fine.

    Many thanks again,

    Matan

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • mschw
    mschw over 2 years ago in reply to matangk2

    Dear Matan,

    it don't know if that helps you, but you can disable Performance Diagnostics in Virtuoso with

    envSetVal("perf" "installAtStartup" 'boolean nil)

    Regards,

    Matthias

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • matangk2
    matangk2 over 2 years ago in reply to mschw

    Dear mschw,

    Thanksop. Hopefully, I can understand how to fix the unrecognized 'gdb'. If not, I'll consider disabling it.

    Best,

    Matan

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 2 years ago in reply to matangk2

    Matan,

    The support status of IC6.1.8 on RHEL8 is that it should work - but it's not routinely tested - hence the lack of "official" support status. You're not the first to try it out and are not particularly early adopters, but you won't see it listed on the downloads.cadence.com site as having this OS as being one of the supported versions.

    Anyway, I just tried myself and ran OK on an RHEL8 machine provided that I was using the latest hotfix, IC6.1.8 ISR29. Using ISR27 as you are using, I get exactly the same error.

    So my suggestion is to move to the later hotfix.

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • matangk2
    matangk2 over 2 years ago in reply to Andrew Beckett

    Excellent,

    I'll try and report.

    Thanks,

    Matan

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • matangk2
    matangk2 over 2 years ago in reply to matangk2

    I Installed Hotfix 618.29 and confirm that the 'gdb' warning is gone.

    Thanks.

    Matan

    • 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