Nemiver: Difference between revisions

From Wikipedia, the free encyclopedia
Content deleted Content added
m Typo fixing, typos fixed: etc) → etc.) using AWB
Removed redlink from See Also
 
(24 intermediate revisions by 18 users not shown)
Line 1: Line 1:
{{Multiple issues|
{{Infobox Software
{{refimprove|date=September 2016}}
{{notability|Products|date=September 2016}}
}}

{{Infobox software
| name = Nemiver
| name = Nemiver
| developer = The Nemiver Team
| developer = The Nemiver Team
| logo = [[Image:nemiver-icon.svg]]
| logo = nemiver-icon.svg
| screenshot = [[Image:nemiver-screenshot.png|200px]]
| screenshot = nemiver-screenshot.png
| released = {{start date|2006|11|10}}
| released = {{Start date and age|2006|11|10}}
| latest release version = 0.9.0
| latest release version = 0.9.6
| latest release date = {{release date|2011|09|10}}
| latest release date = {{Start date and age|2015|09|23}}
| programming language = [[C++ (programming language)|C++]]
| programming language = [[C++]]
| operating system = [[Cross-platform]]
| operating system = [[Cross-platform]]
| platform = [[GNOME]]
| platform = [[GNOME]]
| genre = [[Debugger]]
| genre = [[Debugger]]
| license = [[GNU General Public License]]
| license = [[GNU General Public License]]
| website = http://projects.gnome.org/nemiver/
| website = {{URL|projects.gnome.org/nemiver}}
}}
}}
'''Nemiver''' is a standalone graphical [[C (programming language)|C]] and [[C++ (programming language)|C++]] [[debugger]] that integrates in the [[GNOME]] desktop environment.
'''Nemiver''' is computer [[software]], a graphical standalone [[debugger]] for the programming languages [[C (programming language)|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.
It currently features a backend which uses the well known [[GNU Debugger]] (gdb).
The creator and the current lead developer is Dodji Seketeli.


== Features ==
== Features ==
{{Person|date=November 2011}}


=== General ===
=== General ===
Users can start debugging source code with Nemiver either directly from the command line by typing
<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 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.
A user can start debugging a program with Nemiver either directly from the command line by typing
<code><pre>nemiver <your-program> <prog-arg1> <prog-arg2> ... <prog-argN></pre></code>
or by launching Nemiver first and then using its graphical dialogs to launch the program you want 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, the user is free to set breakpoints, inspect variables, single step, resume the execution of the inferior, etc.


=== Sessions ===
=== 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.

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 for you automatically unless you explicitly request to resume an existing session. On exit, your session will automatically be saved. Information saved with a session includes breakpoints, program arguments, working directory path, environment variables, etc. Additionally, you can save the current session to disk on demand.


=== Extensions ===
=== 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 (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 is a bit more than just a simple GUI debugger. It is actually a platform which can be extended with plug-ins based on dynamically loaded modules.
The libnemivercommon library provides the basic functionality for loading dynamic modules and enabling the plug-in architecture of Nemiver. You can create additional plugins for nemiver, and you can even create entirely 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.).
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 ==


== 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 ==
== See also ==
{{Portal|Free software}}
{{Portal|Free and open-source software}}
* [[Data Display Debugger|DDD]], a Motif debugger front-end
* [[Data Display Debugger]] (DDD), a [[Motif (software)]] debugger front-end
* [[GNU Debugger]] (GDB)
* [[KDbg]], a [[GDB]] front end that integrates well in the [[KDE]] environment
* [[GNU Debugger|GDB]], the GNU Debugger


== External links ==
== External links ==
* [http://projects.gnome.org/nemiver/ The Nemiver homepage]
* {{Official website|projects.gnome.org/nemiver}}

{{GNOME}}


[[Category:Debuggers]]
[[Category:Debuggers]]
[[Category:Free software programmed in C++]]
[[Category:GNOME Developer Tools]]
[[Category:Software that uses GTK]]





Latest revision as of 02:22, 16 May 2023

Nemiver
Developer(s)The Nemiver Team
Initial releaseNovember 10, 2006; 17 years ago (2006-11-10)
Stable release
0.9.6 / September 23, 2015; 8 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[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.

See also[edit]

External links[edit]