GNOME desktop environment is a user-friendly software interface that offers a clean, simple and modern desktop design. It provides an easy-to-use menu system, customizable panels, and a variety of themes and extensions to increase productivity and personalize the user experience.
Nemiver is a standalone graphical debugger that has been designed to integrate seamlessly with the GNOME desktop environment. The project utilizes the widely recognized GNU Debugger gdb as its backend.
One of the standout features of Nemiver is the ability to toggle breakpoints by simply clicking in the margin on the line that you want to break on. You can also hover over a variable name for longer than 1 second, and it will show its value as a tooltip window if the variable is in scope.
Nemiver uses an sqlite database to store information about a debugging session, which means that you can resume your debugging where you left off last time. Whenever you start debugging, a new session will be created for you automatically, and your session will be saved when you exit. Information saved with your session includes breakpoints, program arguments, working directory path, environment variables, and more. You can also save the current session to the database on demand by selecting File > Save Session to Disk. To resume a previously saved debugging session, you can either specify the session ID to the --executesession command line option or select File > Saved Sessions... > [select session] from the User interface.
If the GDB debugger you are using doesn't provide full pathname information for breakpoints, you may need to manually specify which directories to search for source files. This can be done by adding source directories in the Preferences dialog. In the future, there will be a more explicit prompt asking the user to locate the requested file when nemiver can't determine the absolute path of a file on its own.
Nemiver is more than just a GUI debugger. It is actually a platform that can be extended with plugins and dynamically loaded modules. The libnemivercommon library provides the basic functionality for loading dynamic modules and enabling the plugin architecture of Nemiver. You can create additional plugins for Nemiver and even create entirely new perspectives for the Nemiver workbench. Currently, only the debugging perspective is provided, but others could be added in the future, such as a perspective for profiling tools like oprofile, valgrind/massif, etc. Nemiver also provides an event-based debugger library (which currently features a gdb backend, but others could be added in the future) that could be re-used by other projects seeking to implement a debugger as a part of an IDE, for example.
One of the standout features of Nemiver is the ability to toggle breakpoints by simply clicking in the margin on the line that you want to break on. You can also hover over a variable name for longer than 1 second, and it will show its value as a tooltip window if the variable is in scope.
Nemiver uses an sqlite database to store information about a debugging session, which means that you can resume your debugging where you left off last time. Whenever you start debugging, a new session will be created for you automatically, and your session will be saved when you exit. Information saved with your session includes breakpoints, program arguments, working directory path, environment variables, and more. You can also save the current session to the database on demand by selecting File > Save Session to Disk. To resume a previously saved debugging session, you can either specify the session ID to the --executesession command line option or select File > Saved Sessions... > [select session] from the User interface.
If the GDB debugger you are using doesn't provide full pathname information for breakpoints, you may need to manually specify which directories to search for source files. This can be done by adding source directories in the Preferences dialog. In the future, there will be a more explicit prompt asking the user to locate the requested file when nemiver can't determine the absolute path of a file on its own.
Nemiver is more than just a GUI debugger. It is actually a platform that can be extended with plugins and dynamically loaded modules. The libnemivercommon library provides the basic functionality for loading dynamic modules and enabling the plugin architecture of Nemiver. You can create additional plugins for Nemiver and even create entirely new perspectives for the Nemiver workbench. Currently, only the debugging perspective is provided, but others could be added in the future, such as a perspective for profiling tools like oprofile, valgrind/massif, etc. Nemiver also provides an event-based debugger library (which currently features a gdb backend, but others could be added in the future) that could be re-used by other projects seeking to implement a debugger as a part of an IDE, for example.
What's New
Version 0.7.2: N/A