Tags

nemiver 0.5.3-1

first tentative to fix 534695

Nemiver actually is slow when attaching to some targets.
This comes from the fact that nemiver steps over the first C instruction it
finds when attaching to a program. Stepping over might take a lot of time
if for instance there is no debug information for the symbol over which we are trying
to step over.

In this fix tentative, nemiver instead steps into the next machine
instruction instead of the stepping over the first C instruction

svn path=/trunk/; revision=821

nemiver 0.5.2-1

update NEWS

svn path=/trunk/; revision=789

nemiver 0.5.1-1

update NEWS file for 0.5.1 release


svn path=/branches/0.5/; revision=774

nemiver 0.5.0-1

updated NEWS file

svn path=/trunk/; revision=762

nemiver 0.4.0-3

nemiver 0.4.0-2

nemiver 0.4.0-1

Update make release scripts

	* Makefile.am: do not distcheck for release, only dist. Update svn path
	  to point to GNOME svn.

svn path=/trunk/; revision=506

Sun, 21 Jan 2007 14:32:52 +0100 Dodji Seketeli

	* po/POTFILES.in: update path to nemiver.desktop.in
	* NEWS: updated this for 0.3


svn path=/trunk/; revision=367

Sat, 16 Dec 2006 17:05:46 +0100 Dodji Seketeli

	* src/dbgengine/nmv-gdb-engine.cc, configure.ac: reverted changesets
	from ]307,HEAD] because no one should commit to a tag branch.
	I have created branches/0.2 instead.


svn path=/tags/nemiver-0.2.0/; revision=311

Fri, 10 Nov 2006 13:21:02 +0100 Dodji Seketeli

	* Makefile.am: fix the tag-release-only target.


svn path=/trunk/; revision=208

Wed, 08 Nov 2006 21:34:40 +0100 Dodji Seketeli

        * remove this copy. Creating it was an accident.


svn path=/tags/nemiver-0.1.0; revision=205