+++ to secure your transactions use the Bitcoin Mixer Service +++

 

Jump to content

Nemiver: Difference between revisions

From Wikipedia, the free encyclopedia
Content deleted Content added
No edit summary
No edit summary
Line 5: Line 5:
| screenshot = [[Image:nemiver-screenshot.png|200px]]
| screenshot = [[Image:nemiver-screenshot.png|200px]]
| released = {{initial release|2006|11|10}}
| released = {{initial release|2006|11|10}}
| latest_release_version = 0.6.7
| latest_release_version = 0.7.0
| latest_release_date = [[2nd May]] [[2009]]
| latest_release_date = [[2nd July]] [[2009]]
| programming language = [[C++ (programming language)|C++]]
| programming language = [[C++ (programming language)|C++]]
| operating_system = [[Cross-platform]]
| operating_system = [[Cross-platform]]

Revision as of 18:41, 2 July 2009

Nemiver
Developer(s)The Nemiver Team
Initial releaseNovember 10, 2006 (2006-11-10)
Stable release
0.7.0 / 2nd July 2009
Repository
Written inC++
Operating systemCross-platform
PlatformGNOME
TypeDebugger
LicenseGNU General Public License
Websitehttp://projects.gnome.org/nemiver

Nemiver is a standalone graphical C and C++ debugger that integrates well in the GNOME desktop environment. It currently features a backend which uses the well known GNU Debugger GDB.

Features

General

You can start debugging a program 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 use its graphical dialogs to launch the program you want to debug.

Once the inferior program 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

Nemiver stores on disk some basic information about a debugging session so that you can easily resume it later. Whenever you start debugging, a new session is created for you automatically unless you explicitely request to resume an existing session. On exit, your session will automatically be saved. Information saved with your session includes breakpoints, program arguments, working directory path, environment variables, etc. Additionally, you can save the current session to disk on demand.

Extensions

Nemiver is a bit more than just a simple GUI debugger. It is actually a platform which can be extended with plugins based on 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 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 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.

About

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

See also

  • DDD, a Motif debugger front-end
  • KDbg, a GDB front end that integrates well in the KDE environment
  • GDB, the GNU Debugger

External links