Nemiver: Difference between revisions
Jerryobject (talk | contribs) WP:LINKs: updates, adds, cut needless WP:PIPEs. Full terms define before WP:ABBReviations. Add: Template:URL, Template:Official website. Small WP:EoS WP:COPYEDITs. |
Jerryobject (talk | contribs) WP:LINK update, cut needless WP:PIPE. Carriage returns: cut needless in paragraphs, and between items. |
||
Line 6: | Line 6: | ||
| released = {{start date|2006|11|10}} |
| released = {{start date|2006|11|10}} |
||
| latest release version = 0.9.5 |
| latest release version = 0.9.5 |
||
| latest release date = {{ |
| latest release date = {{Start date and age|2013|12|08}} |
||
| programming language = [[C++]] |
| programming language = [[C++]] |
||
| operating system = [[Cross-platform]] |
| operating system = [[Cross-platform]] |
||
Line 14: | Line 14: | ||
| website = {{URL|projects.gnome.org/nemiver}} |
| website = {{URL|projects.gnome.org/nemiver}} |
||
}} |
}} |
||
'''Nemiver''' is computer [[software]], a |
'''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 == |
||
=== General === |
=== General === |
||
Users can start debugging programs with Nemiver either directly from the command line by typing |
Users can start debugging programs with Nemiver either directly from the command line by typing |
||
<code><pre>nemiver <your-program> <prog-arg1> <prog-arg2> ... <prog-argN></pre></code> |
<code><pre>nemiver <your-program> <prog-arg1> <prog-arg2> ... <prog-argN></pre></code> |
||
Line 29: | Line 26: | ||
=== Sessions === |
=== 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 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. |
||
=== Extensions === |
=== Extensions === |
||
⚫ | |||
⚫ | |||
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, 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.). |
||
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 heavily relies on many components of the [[GNOME]] platform, such as [[Gtkmm]]. |
||
Revision as of 06:23, 4 January 2016
Developer(s) | The Nemiver Team |
---|---|
Initial release | November 10, 2006 |
Stable release | 0.9.5
/ December 8, 2013 |
Repository | |
Written in | C++ |
Operating system | Cross-platform |
Platform | GNOME |
Type | Debugger |
License | GNU General Public License |
Website | projects |
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 programs 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 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, users are free to set breakpoints, inspect variables, single step, resume the execution of the inferior, 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.
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.
The libnemivercommon library provides the basic functions to load dynamic modules and enable a 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.).
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.
See also
- 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)