Visual gdb

Author: r | 2025-04-24

Arduino Extended GDB Debugging for Visual Studio 20 - In Brief. Here's an overview of what Visual Micro GDB Debug offers. Gdb Debugging can be used with any sketch and DlangIDE: D language IDE written in D. Supports GDB-MI compatible debuggers. Linux, Windows, MacOS GDB Dexed - GDB commander: Visual debugging with GDB in one of the

cyrus-and/gdb-dashboard: GDB Visual Debugging Interface

Order Area TOCTitle ContentId PageTitle DateApproved MetaDescription 2 cpp GCC on Linux 8ba2e5c6-cb57-4513-bc02-c8b73e6956ad Get Started with C++ on Linux in Visual Studio Code 5/13/2022 Configure the C++ extension in Visual Studio Code to target g++ and GDB on Linux Using C++ on Linux in VS CodeIn this tutorial, you will configure Visual Studio Code to use the GCC C++ compiler (g++) and GDB debugger on Linux. GCC stands for GNU Compiler Collection; GDB is the GNU debugger.After configuring VS Code, you will compile and debug a simple C++ program in VS Code. This tutorial does not teach you GCC, GDB, Ubuntu or the C++ language. For those subjects, there are many good resources available on the Web.If you have trouble, feel free to file an issue for this tutorial in the VS Code documentation repository.PrerequisitesTo successfully complete this tutorial, you must do the following:Install Visual Studio Code.Install the C++ extension for VS Code. You can install the C/C++ extension by searching for 'c++' in the Extensions view (kb(workbench.view.extensions)).Ensure GCC is installedAlthough you'll use VS Code to edit your source code, you'll compile the source code on Linux using the g++ compiler. You'll also use GDB to debug. These tools are not installed by default on Ubuntu, so you have to install them. Fortunately, that's easy.First, check to see whether GCC is already installed. To verify whether it is, open a Terminal window and enter the following command:If GCC isn't installed, run the following command from the terminal window to update the Ubuntu package lists. An out-of-date Linux distribution can sometimes interfere with attempts to install new packages.Next install the GNU compiler tools and the GDB debugger with this command:sudo apt-get install build-essential gdbCreate Hello WorldFrom the terminal window, create an empty folder called projects to store your VS Code projects. Then create a subfolder called helloworld, navigate into it, and open VS Code in that folder by entering the following commands:mkdir projectscd projectsmkdir helloworldcd helloworldcode .The code . command opens VS Code in the current working folder, which becomes your "workspace". As you go through the tutorial, you will create three files in a .vscode folder in the workspace:tasks.json (compiler build settings)launch.json (debugger settings)c_cpp_properties.json (compiler path and IntelliSense settings)Add hello world source code fileIn the File Explorer title bar, select New File and name the file helloworld.cpp.Paste in the following source code:#include #include using namespace std;int main(){ vector msg {"Hello",

GitHub - cyrus-and/gdb-dashboard: Modular visual interface for GDB

The GNU Debugger (GDB) is a powerful and widely used debugging tool in the realm of software development. Created by Richard Stallman and Roland McGrath as part of the GNU Project, GDB was first released in 1986. It is designed to assist developers in finding and resolving bugs in various programming languages, most notably C, C++, Fortran, and more.GDB operates on UNIX-like systems, including Linux and macOS, and provides extensive capabilities for monitoring and controlling the execution of programs. It allows developers to set breakpoints, step through code line-by-line, inspect variables, and modify the execution flow to understand and troubleshoot complex issues in their code.The debugger supports remote debugging, which is particularly useful for embedded systems and cross-platform development, where the target environment differs from the development environment. GDB's versatility is further enhanced through its support for a range of architectures and its integration with other development tools and environments, such as integrated development environments (IDEs) like Eclipse and Visual Studio Code.One of the key features of GDB is its ability to examine the state of a program at any given point during its execution. This includes viewing the call stack, examining memory contents, and inspecting the values of variables and expressions. Additionally, GDB offers scripting capabilities using its command language, which allows developers to automate repetitive tasks and customize the debugging process to suit their needs.Over the years, GDB has evolved with contributions from the open-source community, continually improving its functionality and performance. Its robustness and reliability have made it an indispensable tool for developers aiming to produce high-quality, error-free software.GDB's impact on software development is profound, providing the means to delve deeply into program behavior, identify subtle bugs, and optimize performance. As a cornerstone of the GNU Project, GDB exemplifies the power of open-source collaboration and remains a vital tool for developers around the world.The GNU Debugger (GDB) is a powerful and widely used debugging tool in the realm of software development. Created by Richard Stallman and Roland McGrath as part of the GNU Project, GDB was first released in 1986. It is designed to assist developers in

Visual GDB Debug Error – sh: gdb: command not found

Early Access Program NewsCLion Starts the 2022.2 EAP: Colorized Ninja output, Embedded GDB Server Wizard, Updated CMake Presets Integration The CLion 2022.2 Early Access Preview program starts today!Give the free EAP builds a try and let us know what you think about the changes! Share your feedback in the comments or submit it to our issue tracker.Build 222.2270.30 is available from our website via the Toolbox App or as a snap package (if you are using Ubuntu). Note that if you are on macOS, there is a separate build for Apple Silicon (M1 chip).DOWNLOAD CLION 2022.2 EAPHere are the main highlights:Colorized output for Ninja generator is now enabled in CLion.A new wizard was added for Embedded GDB Server run configurations.Code analysis and refactorings became more accurate.Code completion was improved.CMake Presets integration got updated.Colorized Ninja outputColorized compiler output helps dealing with compilation errors much faster. That’s why we contributed to CMake and implemented a way to enable colorized output for the Ninja generator in CMake in CLion by default. The change is now in CMake master and will be released as a part of the 3.24 release of CMake. It introduces the CMAKE_COLOR_DIAGNOSTICS CMake variable that controls the following:Whether CMake should enable colored compiler diagnostics via compiler flags.The CMAKE_COLOR_MAKEFILE variable.Additionally, we added support for the CMAKE_COLOR_DIAGNOSTICS environment variable, which controls the default value for the CMAKE_COLOR_DIAGNOSTICS variable. CLion now always adds the CMAKE_COLOR_DIAGNOSTICS=ON environment variable when re-loading the CMake project. This ensures that there will be colored diagnostics for both Ninja and Makefile generators.Note, that the default bundled CMake version is 3.22 for now. To get the colorized output, you need to build CMake 3.24 and use it in the CLion toolchain.A new wizard for Embedded GDB Server run configurationsGDB servers are often used to debug on-chip. In CLion, you can use them by creating the Embedded GDB Server run/debug configuration. Previously, you had to create such configurations manually, but now there’s a wizard available for this purpose. This wizard helps with creating Embedded GDB Server run configuration with the predefined GDB server arguments corresponding to the GDB server type selected in the wizard settings.Launch the new wizard via Run | New Embedded Configuration. In the dialog that opens, enter the configuration name and the preferred type of the GDB Server:Segger JLinkQEMU emulatorPyOCDSt-utilSTM32CubeIDE ST-LINK GDB serverPE Micro (OpenSDA)When the GDB server’s expected name is found in PATH, the location of the. Arduino Extended GDB Debugging for Visual Studio 20 - In Brief. Here's an overview of what Visual Micro GDB Debug offers. Gdb Debugging can be used with any sketch and DlangIDE: D language IDE written in D. Supports GDB-MI compatible debuggers. Linux, Windows, MacOS GDB Dexed - GDB commander: Visual debugging with GDB in one of the

Using GDB with GDB Server within Visual Studio Code

Finding and resolving bugs in various programming languages, most notably C, C++, Fortran, and more.GDB operates on UNIX-like systems, including Linux and macOS, and provides extensive capabilities for monitoring and controlling the execution of programs. It allows developers to set breakpoints, step through code line-by-line, inspect variables, and modify the execution flow to understand and troubleshoot complex issues in their code.The debugger supports remote debugging, which is particularly useful for embedded systems and cross-platform development, where the target environment differs from the development environment. GDB's versatility is further enhanced through its support for a range of architectures and its integration with other development tools and environments, such as integrated development environments (IDEs) like Eclipse and Visual Studio Code.One of the key features of GDB is its ability to examine the state of a program at any given point during its execution. This includes viewing the call stack, examining memory contents, and inspecting the values of variables and expressions. Additionally, GDB offers scripting capabilities using its command language, which allows developers to automate repetitive tasks and customize the debugging process to suit their needs.Over the years, GDB has evolved with contributions from the open-source community, continually improving its functionality and performance. Its robustness and reliability have made it an indispensable tool for developers aiming to produce high-quality, error-free software.GDB's impact on software development is profound, providing the means to delve deeply into program behavior, identify subtle bugs, and optimize performance. As a cornerstone of the GNU Project, GDB exemplifies the power of open-source collaboration and remains a vital tool for developers around the world.

dmhacker/graphical-gdb: Visual GDB command line tool - GitHub

Multiple AMD groups collaborated to develop a new powerful graphics optimization tool using custom, built-in, hardware thread-tracing correlated with rich data from the software stack. This tool is quickly becoming the must-have graphics optimization tool. I oversaw the cross-functional development of many fundamental building blocks for the tool including its interoperability with RenderDoc. Check out the video and blog post.Technologies: Direct3D 12, Vulkan, SQTT, GCN, C/C++ and Qt.Continuing on the AMD initiative to develop debug solutions for AMD platforms, I am leading global teams to extend the GCN core debugger technology from supporting APUs on HSA to the discrete GPUs running on Radeon Open Compute platforms (ROCm). This core debugger technology is used by ROCm GDB and CodeXL 2.0 to allow debugging of GPU kernels on ROCm. ROCm GDB can support debugging all language runtimes built on top of ROCm. Check out the blog post.Technologies: ROCm, HCC, HIP, GCN, C/C++ and GDB internals.I led AMD hardware, firmware, driver, runtime, compiler and tools engineers and architects to define and develop the software and hardware foundation to enable hardware-based debugger based on AMD Graphics Core Next (GCN) GPUs. We extended GDB with the ability to seamlessly debug host CPU and GPU kernel code for HSA applications as the first application of this core debugger technology.The hardware-based implementation provided in the GCN debugger technology is a vast improvement over the previous debugger implementation provided in the CodeXL OpenCL™ debugger which relies on repeated kernel recompilation and replay. Using the GCN debugger technology, we are able to stop all the massively parallel threads in the GPU at a breakpoint, inspect the machine state by reading registers and memory, and then resume and execute all the GPU threads. The instruction pointer at the ISA level can be correlated with the HSAIL line.Technologies: HSAIL, GCN, C/C++ and GDB.I led the GPU Compute Tools team that develops the core software technology to enable debugging OpenCL™ kernel on AMD Radeon GPUs and APUs. You can view variables, set breakpoints and run to breakpoints in an OpenCL kernel executing on the GPUs. These operations can be performed inside the familiar Visual Studio environment and with a single machine. This is the first OpenCL GPU kernel debugger in the industry. This core technology has been incorporated into CodeXL (previously gDebugger), a comprehensive tool for debugging OpenCL applications. The team was recognized with the company-wide AMD Executive Spotlight Award in 2011.Technologies: C++ and OpenCL™.The AMD APP Profiler (formerly ATI Stream Profiler) is a Microsoft Visual Studio® integrated runtime profiler that gathers performance data from the GPU as your application runs. This information can then be used by developers to discover where the bottlenecks are in their OpenCL™ application and find ways

Cortex-GDB - Visual Studio Marketplace

I tried to run gdb on keepassxc, but encountered an unfamiliar error:$ gdb /usr/bin/keepassxcGNU gdb (Ubuntu 8.1-0ubuntu3) 8.1.0.20180409-gitCopyright (C) 2018 Free Software Foundation, Inc.License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it.There is NO WARRANTY, to the extent permitted by law. Type "show copying"and "show warranty" for details.This GDB was configured as "x86_64-linux-gnu".Type "show configuration" for configuration details.For bug reporting instructions, please see:.Find the GDB manual and other documentation resources online at:.For help, type "help".Type "apropos word" to search for commands related to "word"...Reading symbols from /usr/bin/keepassxc...Reading symbols from /usr/lib/debug/.build-id/80/9b2f2d5157a8872dcd140977ba01adfca0e7ad.debug...done.done.(gdb) runStarting program: /usr/bin/keepassxc [Thread debugging using libthread_db enabled]Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".Cannot find user-level thread for LWP 15111: generic error(gdb) quitThe GDB FAQ gives some common causes for errors like"Cannot find user-level thread for LWP 15111: generic error"(the number after LWP is different each time): 9. GDB reports "Cannot find user-level thread for LWP 23957: generic error", how do I fix this? There are several common causes: You have a mismatch between libthread_db.so.1 and libpthread.so.0 (this most often happens when you have multiple installations of glibc, or when you debug a program on remote target, and host and target have different glibc versions). You are using 64-bit debugger to debug 32-bit program, and your kernel has a 32-bit ptrace emulation bug. FIXME: add reference to specific kernel fix. This has also been known to happen when one of DOSEMU's signal handlers is invoked from DPMI context, where the $gs register has a value different from what GDB and/or libthread_db.so.0 expect; SamuelBronson found running the program under gdbserver to alleviate the problem, at least with version 6.8.50.20090620-cvs on i386. am running a 64-bit machine with i386 enabled:$ getconf LONG_BIT64$ dpkg --print-foreign-architecturesi386$ dlocate libthread_db.so.1libc6-i386: /lib32/libthread_db.so.1libc6:i386: /lib/i386-linux-gnu/libthread_db.so.1libc6:amd64: /lib/x86_64-linux-gnu/libthread_db.so.1$ dlocate libpthread.so.0libc6-i386: /lib32/libpthread.so.0libc6:i386: /lib/i386-linux-gnu/libpthread.so.0libc6:amd64: /lib/x86_64-linux-gnu/libpthread.so.0and keepassxc does use libpthread.so.0:$ ldd /usr/bin/keepassxc | grep thread libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f889b803000)but so does texstudio:$ ldd /usr/bin/texstudio | grep thread libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007efd2a09e000)and I can load texstudio just fine.$ gdb /usr/bin/texstudio GNU gdb (Ubuntu 8.1-0ubuntu3) 8.1.0.20180409-gitCopyright (C) 2018 Free Software Foundation, Inc.License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it.There is NO WARRANTY, to the extent permitted by law. Type "show copying"and "show warranty" for details.This GDB was configured as "x86_64-linux-gnu".Type "show configuration" for configuration details.For bug reporting instructions, please see:.Find the GDB manual and other documentation resources online at:.For help, type "help".Type "apropos word" to search for commands related to "word"...Reading symbols from /usr/bin/texstudio...Reading symbols from /usr/lib/debug/.build-id/8c/49a9b8c208b2b75fbd3dc0ad9d9bf009886a47.debug...done.done.(gdb) runStarting program: /usr/bin/texstudio [Thread debugging using libthread_db enabled]Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".[New Thread 0x7fffe915a700 (LWP 20816)][New Thread 0x7fffda55f700 (LWP 20822)][New Thread 0x7fffcb7e9700 (LWP 20823)][New Thread 0x7fffca2fe700 (LWP 20824)][New Thread 0x7fffc96d9700 (LWP 20825)][New Thread 0x7fffc0937700 (LWP 20826)][Thread 0x7fffc0937700 (LWP 20826) exited][Thread 0x7fffc96d9700 (LWP 20825) exited][Thread 0x7fffca2fe700 (LWP 20824) exited][Thread 0x7fffe915a700 (LWP 20816) exited][Thread 0x7fffcb7e9700 (LWP 20823) exited][Thread 0x7fffda55f700 (LWP 20822) exited][Inferior 1 (process 20796) exited normally](gdb) quitFurthermore, keepassxc is a 64-bit executable:$ file /usr/bin/keepassxc/usr/bin/keepassxc: ELF 64-bit LSB shared object,

GDB DAP - Visual Studio Marketplace

Bad system callerror?6.11. Why the undefined reference to WinMain@16?6.12. How do I use Windows API calls?6.13. How do I compile a Windows executable that doesn't use Cygwin?6.14. Can I build a Cygwin program that does not require cygwin1.dll at runtime?6.15. Can I link with both MSVCRT*.DLL and cygwin1.dll?6.16. How do I make the console window go away?6.17. Why does make complain about a "missing separator"?6.18. Why can't we redistribute Microsoft's Windows API headers?6.19. How do I use cygwin1.dll with Visual Studio or Mingw-w64?6.20. How do I link against a .lib file?6.21. How do I build Cygwin on my own?6.22. I may have found a bug in Cygwin, how can I debug it (the symbols in gdb look funny)?6.23. How can I compile Cygwin for an unsupported platform (PowerPC, Alpha, ARM, Itanium)?6.24. How can I adjust the heap/stack size of an application?6.25. How can I find out which DLLs are needed by an executable?6.26. How do I build a DLL?6.27. How can I set a breakpoint at mainCRTStartup?6.28. How can I debug what's going on?6.29. Can I use a system trace mechanism instead?6.30. How does gdb handle signals?6.31. The linker complains that it can't find something.6.32. Why do I get an error using struct stat64?6.33. Can you make DLLs that are linked against libc ?6.34. Where is malloc.h?6.35. Can I use my own malloc?6.36. Can I mix objects compiled with msvc++ and gcc?6.37. Can I use the gdb debugger to debug programs built by VC++?6.38. Shell scripts aren't running properly from my makefiles?6.39. What preprocessor macros do I need to know about?6.40. How should I port my Unix GUI to Windows?6.1.How do I contribute a package?If you are willing to be a package maintainer, great! We urgently needvolunteers to prepare and maintain packages, because the priority of theCygwin Team is Cygwin. Arduino Extended GDB Debugging for Visual Studio 20 - In Brief. Here's an overview of what Visual Micro GDB Debug offers. Gdb Debugging can be used with any sketch and

Visual Studio GDB Debugger - YouTube

Payment A declaration of dividend to the Government of Grenada for the fourth consecutive year. 2019 proved to be another successful year both financially and operationally for the Grenada Development Bank. Grenada Development Bank Celebrates 55 Development is not simply part of the Bank name, but an integral part of its identity. Members of the Board of Directors, Management and Staff gathered to commemorate this historic occasion with the planting of a Flamboyant tree. Small Hoteliers Loan Programme $900K Already Approved Under Government's Revised Programme $900K from the revised Government of Grenada’s Small Hoteliers Loan programme available through the Grenada Development Bank has already been approved. Small Business Owners Trained by GDB Business Support and Development Service 19 small business owners can now boast of being more proficient in bookkeeping. This after completing a workshop organised and hosted by the GDB. GDB Declares Dividends GDB Declares Dividends 2018 has proven to be another profitable year for the GDB so much so that for the 3rd consecutive year in the Bank’s history, dividends were paid to the Government of Grenada, its sole shareholder. School Support GDB Supports Hillsborough Secondary School in 2018 For the 2nd consecutive year, the Grenada Development Bank provided sponsorship to the Hillsborough Secondary School for their 13th Annual Awards Ceremony. GDB Declares Dividends GDB pays dividends to Government of Grenada 2017 has proven to be another profitable year for the GDB. For the 2nd consecutive year in the Bank’s history, it was able to pay dividends to its sole shareholder the Government of Grenada. Best Performing Development Bank GDB, best performing development bank in OECS With a current non-performing loan ratio of just under 5% the GDB can boast of being the best performing development bank in the OECS sub-region in terms of non-performing loans. Satisfied SBDF Customers Customer Lauds Small Business Development Fund Mrs. Janet Bennett-Whint, owner of Spice Isle Plantation is one of many satisfied Small Business Development Fund customers. School Support GDB Supports Hillsborough Secondary School in 2017 Grenada Development Bank was welcomed on board as a first time sponsor for the Hillsborough Secondary

Using GDB in Visual Studio - gpac.io

Find out which DLLs are needed by an executable?objdump -p provides this information, but is rather verbose.cygcheck will do this much more concisely, and operatesrecursively, provided the command is in your path.6.26.How do I build a DLL?There's documentation that explains the process in the Cygwin User'sGuide here: can I set a breakpoint at mainCRTStartup? Set a breakpoint in gdb with b *0x401000 (for i686), or b *0x100401000 (for x86_64). This entrypoint address can be computed as the sum of the ImageBase and AddressOfEntryPoint values given by objdump -p. Note that the DllMain entrypoints for linked DLLs will have been executed before this breakpoint is hit. (It may be necessary to use the gdb command set disable-randomization on to turn off ASLR for the debuggee to prevent the base address getting randomized.)6.28.How can I debug what's going on?You can debug your application using gdb. Make sure youcompile it with the -g flag! If your application calls functions inMS DLLs, gdb will complain about not being able to load debug informationfor them when you run your program. This is normal since these DLLsdon't contain debugging information (and even if they did, that debuginfo would not be compatible with gdb).6.29.Can I use a system trace mechanism instead?Yes. You can use the strace.exe utility to run other cygwinprograms with various debug and trace messages enabled. For informationon using strace, see the Cygwin User's Guide.6.30.How does gdb handle signals?gdb maps known Windows exceptions to signals such as SIGSEGV, SIGFPE, SIGTRAP,SIGINT and SIGILL. Other Windows exceptions are passed on to the handler (ifany), and reported as an unknown signal if an unhandled (second chance)exception occurs.There is also an experimental feature to notify gdb of purely Cygwin signalslike SIGABRT, SIGHUP or SIGUSR1. This currently has some known problems, forexample, single-stepping from these signals may not work as. Arduino Extended GDB Debugging for Visual Studio 20 - In Brief. Here's an overview of what Visual Micro GDB Debug offers. Gdb Debugging can be used with any sketch and DlangIDE: D language IDE written in D. Supports GDB-MI compatible debuggers. Linux, Windows, MacOS GDB Dexed - GDB commander: Visual debugging with GDB in one of the

GDB Debug - Visual Studio Marketplace

[NVIDIA CUDA/ ]cuda-gdb-11-1 11.1.105-1 [NVIDIA CUDA/ ]cuda-gdb-11-2 11.2.152-1 [NVIDIA CUDA/ ]cuda-gdb-11-3 11.3.109-1 [NVIDIA CUDA/ ]cuda-gdb-11-4 11.4.120-1 [NVIDIA CUDA/ ]cuda-gdb-11-5 11.5.114-1 [NVIDIA CUDA/ ]cuda-gdb-11-6 11.6.124-1 [NVIDIA CUDA/ ]cuda-gdb-11-7 11.7.91-1 [NVIDIA CUDA/ ]cuda-gdb-src-10-0 10.0.130-1 [NVIDIA CUDA/ ]└── Contains the source code for cuda-gdbcuda-gdb-src-10-1 10.1.243-1 [NVIDIA CUDA/ ]└── Contains the source code for cuda-gdbcuda-gdb-src-10-2 10.2.89-1 [NVIDIA CUDA/ ]└── Contains the source code for cuda-gdbcuda-gdb-src-11-0 11.0.221-1 [NVIDIA CUDA/ ]└── Contains the source code for cuda-gdbcuda-gdb-src-11-1 11.1.105-1 [NVIDIA CUDA/ ]└── Contains the source code for cuda-gdbcuda-gdb-src-11-2 11.2.152-1 [NVIDIA CUDA/ ]└── Contains the source code for cuda-gdbcuda-gdb-src-11-3 11.3.109-1 [NVIDIA CUDA/ ]└── Contains the source code for cuda-gdbcuda-gdb-src-11-4 11.4.120-1 [NVIDIA CUDA/ ]└── Contains the source code for cuda-gdbcuda-gdb-src-11-5 11.5.114-1 [NVIDIA CUDA/ ]└── Contains the source code for cuda-gdbcuda-gdb-src-11-6 11.6.124-1 [NVIDIA CUDA/ ]└── Contains the source code for cuda-gdbcuda-gdb-src-11-7 11.7.91-1 [NVIDIA CUDA/ ]└── Contains the source code for cuda-gdbcuda-gpu-library-advisor-10-0 10.0.130-1 [NVIDIA CUDA/ ]cuda-gpu-library-advisor-10-1 10.1.243-1 [NVIDIA CUDA/ ]cuda-keyring 1.0-1 [NVIDIA CUDA/ ]cuda-libraries-10-0 10.0.130-1 [NVIDIA CUDA/ ]cuda-libraries-10-1 10.1.243-1 [NVIDIA CUDA/ ]cuda-libraries-10-2 10.2.89-1 [NVIDIA CUDA/ ]cuda-libraries-11-0 11.0.3-1 [NVIDIA CUDA/ ]cuda-libraries-11-1 11.1.1-1 [NVIDIA CUDA/ ]cuda-libraries-11-2 11.2.2-1 [NVIDIA CUDA/ ]cuda-libraries-11-3 11.3.1-1 [NVIDIA CUDA/ ]cuda-libraries-11-4 11.4.4-1 [NVIDIA CUDA/ ]cuda-libraries-11-5 11.5.2-1 [NVIDIA CUDA/ ]cuda-libraries-11-6 11.6.2-1 [NVIDIA CUDA/ ]cuda-libraries-11-7 11.7.1-1 [NVIDIA CUDA/ ]cuda-libraries-dev-10-0 10.0.130-1 [NVIDIA CUDA/ ]cuda-libraries-dev-10-1 10.1.243-1 [NVIDIA CUDA/ ]cuda-libraries-dev-10-2 10.2.89-1 [NVIDIA CUDA/ ]cuda-libraries-dev-11-0 11.0.3-1 [NVIDIA CUDA/ ]cuda-libraries-dev-11-1 11.1.1-1 [NVIDIA CUDA/ ]cuda-libraries-dev-11-2 11.2.2-1 [NVIDIA CUDA/ ]cuda-libraries-dev-11-3 11.3.1-1 [NVIDIA CUDA/ ]cuda-libraries-dev-11-4 11.4.4-1 [NVIDIA CUDA/ ]cuda-libraries-dev-11-5 11.5.2-1 [NVIDIA CUDA/ ]cuda-libraries-dev-11-6 11.6.2-1 [NVIDIA CUDA/ ]cuda-libraries-dev-11-7 11.7.1-1 [NVIDIA CUDA/ ]cuda-license-10-0 10.0.130-1 [NVIDIA CUDA/ ]cuda-license-10-1 10.1.243-1 [NVIDIA CUDA/ ]cuda-license-10-2 10.2.89-1 [NVIDIA CUDA/ ]cuda-memcheck-10-0 10.0.130-1 [NVIDIA CUDA/ ]cuda-memcheck-10-1 10.1.243-1 [NVIDIA CUDA/ ]cuda-memcheck-10-2 10.2.89-1 [NVIDIA CUDA/ ]cuda-memcheck-11-0 11.0.221-1 [NVIDIA CUDA/ ]cuda-memcheck-11-1 11.1.105-1 [NVIDIA CUDA/ ]cuda-memcheck-11-2 11.2.152-1 [NVIDIA CUDA/ ]cuda-memcheck-11-3 11.3.109-1 [NVIDIA CUDA/ ]cuda-memcheck-11-4 11.4.120-1 [NVIDIA CUDA/ ]cuda-memcheck-11-5 11.5.114-1 [NVIDIA CUDA/ ]cuda-memcheck-11-6 11.6.124-1 [NVIDIA CUDA/ ]cuda-memcheck-11-7 11.7.91-1 [NVIDIA CUDA/ ]cuda-minimal-build-10-0 10.0.130-1 [NVIDIA CUDA/ ]cuda-minimal-build-10-1 10.1.243-1 [NVIDIA CUDA/ ]cuda-minimal-build-10-2 10.2.89-1 [NVIDIA CUDA/ ]cuda-minimal-build-11-0 11.0.3-1 [NVIDIA CUDA/ ]cuda-minimal-build-11-1 11.1.1-1 [NVIDIA CUDA/ ]cuda-minimal-build-11-2 11.2.2-1 [NVIDIA CUDA/ ]cuda-minimal-build-11-3 11.3.1-1 [NVIDIA CUDA/ ]cuda-minimal-build-11-4 11.4.4-1 [NVIDIA CUDA/ ]cuda-minimal-build-11-5 11.5.2-1 [NVIDIA CUDA/ ]cuda-minimal-build-11-6 11.6.2-1 [NVIDIA CUDA/ ]cuda-minimal-build-11-7 11.7.1-1 [NVIDIA CUDA/ ]cuda-misc-headers-10-0 10.0.130-1 [NVIDIA CUDA/ ]cuda-misc-headers-10-1 10.1.243-1 [NVIDIA CUDA/ ]cuda-misc-headers-10-2 10.2.89-1 [NVIDIA CUDA/ ]cuda-npp-10-0 10.0.130-1 [NVIDIA CUDA/ ]cuda-npp-10-1 10.1.243-1 [NVIDIA CUDA/ ]cuda-npp-10-2 10.2.89-1 [NVIDIA CUDA/ ]cuda-npp-dev-10-0 10.0.130-1 [NVIDIA CUDA/ ]cuda-npp-dev-10-1 10.1.243-1 [NVIDIA CUDA/ ]cuda-npp-dev-10-2 10.2.89-1 [NVIDIA CUDA/ ]cuda-nsight-10-0 10.0.130-1 [NVIDIA CUDA/ ]cuda-nsight-10-1 10.1.243-1 [NVIDIA CUDA/ ]cuda-nsight-10-2 10.2.89-1 [NVIDIA CUDA/ ]cuda-nsight-11-0 11.0.221-1 [NVIDIA CUDA/ ]cuda-nsight-11-1 11.1.105-1 [NVIDIA CUDA/ ]cuda-nsight-11-2 11.2.152-1 [NVIDIA CUDA/ ]cuda-nsight-11-3 11.3.109-1 [NVIDIA CUDA/ ]cuda-nsight-11-4 11.4.120-1 [NVIDIA CUDA/ ]cuda-nsight-11-5 11.5.114-1 [NVIDIA CUDA/ ]cuda-nsight-11-6 11.6.124-1 [NVIDIA CUDA/ ]cuda-nsight-11-7 11.7.91-1 [NVIDIA CUDA/ ]cuda-nsight-compute--10-0 10.0.130-1 [NVIDIA CUDA/ ]cuda-nsight-compute-10-0 10.0.130-1 [NVIDIA CUDA/ ]cuda-nsight-compute-10-1 10.1.243-1 [NVIDIA CUDA/ ]cuda-nsight-compute-10-2 10.2.89-1 [NVIDIA CUDA/ ]cuda-nsight-compute-11-0 11.0.3-1 [NVIDIA CUDA/ ]cuda-nsight-compute-11-1 11.1.1-1 [NVIDIA CUDA/ ]cuda-nsight-compute-11-2 11.2.2-1 [NVIDIA CUDA/ ]cuda-nsight-compute-11-3 11.3.1-1 [NVIDIA CUDA/ ]cuda-nsight-compute-11-4 11.4.4-1 [NVIDIA CUDA/ ]cuda-nsight-compute-11-5 11.5.2-1 [NVIDIA CUDA/ ]cuda-nsight-compute-11-6 11.6.2-1 [NVIDIA CUDA/ ]cuda-nsight-compute-11-7 11.7.1-1 [NVIDIA CUDA/ ]cuda-nsight-systems-10-1 10.1.243-1 [NVIDIA CUDA/ ]cuda-nsight-systems-10-2 10.2.89-1 [NVIDIA CUDA/ ]cuda-nsight-systems-11-0 11.0.3-1 [NVIDIA CUDA/ ]cuda-nsight-systems-11-1 11.1.1-1 [NVIDIA CUDA/ ]cuda-nsight-systems-11-2 11.2.2-1 [NVIDIA CUDA/ ]cuda-nsight-systems-11-3 11.3.1-1 [NVIDIA CUDA/ ]cuda-nsight-systems-11-4 11.4.4-1 [NVIDIA CUDA/ ]cuda-nsight-systems-11-5 11.5.2-1 [NVIDIA CUDA/