Nemiver: Difference between revisions

Nemiver
Developer(s)	The Nemiver Team
Initial release	November 10, 2006; 17 years ago
Stable release	0.9.6 / September 23, 2015; 8 years ago
Repository	gitlab.gnome.org/GNOME/nemiver.git ;
Written in	C++
Operating system	Cross-platform
Platform	GNOME
Type	Debugger
License	GNU General Public License
Website	projects.gnome.org/nemiver

Browse history interactively

← Previous edit

Content deleted Content added

VisualWikitext

Inline

Latest revision as of 02:22, 16 May 2023

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[edit]

General[edit]

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[edit]

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[edit]

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[edit]

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

External links[edit]

Official website

This GNOME-related article is a stub. You can help Wikipedia by expanding it.

@@ Line 1: / Line 1: @@
+{{Multiple issues|
+{{refimprove|date=September 2016}}
+{{notability|Products|date=September 2016}}
+}}
 {{Infobox software
 | name = Nemiver
@@ Line 19: / Line 24: @@
 === General ===
-Users can start debugging programs with Nemiver either directly from the command line by typing
+Users can start debugging source code with Nemiver either directly from the command line by typing
-<code><pre>nemiver <your-program> <prog-arg1> <prog-arg2> ... <prog-argN></pre></code>
+<pre>nemiver <your-program> <prog-arg1> <prog-arg2> ... <prog-argN></pre>
-or by launching Nemiver first and then using its graphical dialogs to launch the program you want to debug.
+or by launching Nemiver first and then using its graphical dialogs to launch the program to debug.
-Once the program to be debugged is launched, Nemiver automatically sets a breakpoint in its main function. Once the program is stopped in the main function, users are free to set breakpoints, inspect variables, single step, resume the execution of the inferior, etc.
+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 on disk some basic information about a debugging session so that it can easily 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.
+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 bit more than just a simple [[graphical user interface]] (GUI) debugger. It is a platform which can be extended with plug-ins based on dynamically loaded modules.
+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 (computing)|plug-in]] architecture, allowing Nemiver to be extended using additional plugins, and even new perspectives for the nemiver workbench. Currently, only the debugging perspective is provided, but others could be added in the future (e.g., a perspective for profiling tools such as OProfile, Valgrind-Massif, etc.).
+The libnemivercommon library provides the basic functions to load dynamic modules and enable a [[Plug-in (computing)|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.
+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 heavily relies on many components of the [[GNOME]] platform, such as [[Gtkmm]].
+Nemiver is written in [[C++]], and relies on many components of the [[GNOME]] platform, such as [[Gtkmm]].
 == See also ==
-{{Portal|Free software}}
+{{Portal|Free and open-source software}}
 * [[Data Display Debugger]] (DDD), a [[Motif (software)]] debugger front-end
-* [[KDbg]], a GDB front end that integrates well in the [[KDE]] environment
 * [[GNU Debugger]] (GDB)
@@ Line 52: / Line 56: @@
 [[Category:Free software programmed in C++]]
 [[Category:GNOME Developer Tools]]
-[[Category:Software that uses GTK+]]
+[[Category:Software that uses GTK]]
 {{GNOME-stub}}