This article has multiple issues. Please help improve it or discuss these issues on the talk page. (Learn how and when to remove these template messages) This article needs additional citations for verification. Please help improve this article by adding citations to reliable sources. Unsourced material may be challenged and removed.Find sources: "Nemiver" – news · newspapers · books · scholar · JSTOR (September 2016) (Learn how and when to remove this template message) The topic of this article may not meet Wikipedia's notability guidelines for products and services. Please help to demonstrate the notability of the topic by citing reliable secondary sources that are independent of the topic and provide significant coverage of it beyond a mere trivial mention. If notability cannot be shown, the article is likely to be merged, redirected, or deleted.Find sources: "Nemiver" – news · newspapers · books · scholar · JSTOR (September 2016) (Learn how and when to remove this template message) (Learn how and when to remove this template message)
Nemiver
Developer(s)The Nemiver Team
Initial releaseNovember 10, 2006; 15 years ago (2006-11-10)
Stable release
0.9.6 / September 23, 2015; 6 years ago (2015-09-23)
Repository
Written inC++
Operating systemCross-platform
PlatformGNOME
TypeDebugger
LicenseGNU General Public License
Websiteprojects.gnome.org/nemiver

Nemiver is computer software, a graphical standalone debugger for the programming languages C and C++, which integrates in the GNOME desktop environment. It currently features a backend which uses the well known GNU Debugger (GDB). The creator and the current lead developer is Dodji Seketeli.

Features

General

Users can start debugging source code with Nemiver either directly from the command line by typing

nemiver <your-program> <prog-arg1> <prog-arg2> ... <prog-argN>

or by launching Nemiver first and then using its graphical dialogs to launch the program to debug.

Once the program is launched, Nemiver automatically sets a breakpoint in its main function. Once the program has stopped at the main function, users are free to set breakpoints, inspect variables, investigate the behavior of functions within the code, resume the execution of the program etc.

Sessions

Nemiver stores some basic information about a debugging session on disk, so that the session can be resumed later. Whenever debugging is started, a new session is created automatically, unless it is explicitly requested to resume an extant session. On exit, the session is automatically saved. Information saved with a session includes breakpoints, program arguments, working directory path, environment variables, etc. Also, the current session can be saved to disk on demand.

Extensions

Nemiver is a more than a graphical user interface (GUI) debugger for computer code. It is a platform which can be extended with plugins.

The libnemivercommon library provides the basic functions to load dynamic modules and enable a plug-in architecture, and allowing new functionality for the Nemiver workbench. Currently, only the debugging functionality is provided, but others could be added, for example profiling tools such as OProfile, or Valgrind-Massif.

Nemiver also provides an event-based debugger library (which currently features a GDB back-end, 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 integrated development environment (IDE), for example.

About

Nemiver is written in C++, and relies on many components of the GNOME platform, such as Gtkmm.

See also