KDevelop4 testing - boost backtraces

Hello

David, as you asked I have two backtraces of two small
programs using boost libraries. I use boost a lot and mostly
they are couse of my parsing crashes.

time.cpp:

#include
"boost/date_time/posix_time/posix_time.hpp"
#include <iostream>

   int
   main()
   {
     using namespace boost::posix_time;
     using namespace boost::gregorian;

     ptime now = microsec_clock::local_time();
     time_iterator titr(now, milliseconds(800));

	for (int i = 0 ; i < 10 ; ++titr, ++i)
	{
		ptime later = now + milliseconds (800);
	      std::cout << to_simple_string(*titr) <<
std::endl;
	      std::cout << to_simple_string(now) <<
std::endl;
	      std::cout << to_simple_string(later) <<
std::endl;

		  do {
			  now = microsec_clock::local_time();
			  } while (now < later);
	}

     return 0;
   }

Log is availible here: http://ww
w.haze.ehost.pl/pub/kdev4/time.txt (about 3MB)

and boostregex.cpp:

#include <iostream>
#include <boost/regex.hpp>
#include <string>

int main ()
{
     //^C08,12
     //2nd group is fgColor, 4th group is bgColor
     boost::regex colorRegex
("\^C(([0-9]{1,2})(,([0-9]{1,2})?)?)?");
     boost::smatch results;
     std::string line ("^C11");

     boost::regex_match (line, results, colorRegex);

     std::cout << "second group: '" <<
results[2] << "' and again: '" <<
results[2] << "'" << std::endl;

     return 0;
}

Log is availible here: htt
p://www.haze.ehost.pl/pub/kdev4/boostregex.txt (about
3MB)

On the side note:

I like hilighting a word that you click on. It would be nice
to have some option like "persistent hilight". In
most editors you have Search option that hilights your
searched word, but hilight quickly disappears as soon as you
move cursor/search other word/quit search mode. I have a
plugin for Vim called mark.vim which is capable to hilight
up to 6 words I choose like this: http:
//www.haze.ehost.pl/pub/kdev4/vim-mark.png . It would be
another killer-app for KDevelop/Kate 

Keep up the good work,
Greetings,
Tomasz Kalkosiński

_______________________________________________
KDevelop-devel mailing list
KDevelop-develkdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel

Hi! Thanks for your Testing. Unfortunately the you didn't
send backtraces but 
logs, and those do not contain useful information for your
specific crashes. 
What I need is backtraces done with gdb.

You know how to create those? Just run "gdb
kdevelop", input "r" to the gdb 
console, then when the crash happens the console is back.
Type "thread apply 
all backtrace" into it, and send the full output you
get from that command.

Greetings, David

_______________________________________________
KDevelop-devel mailing list
KDevelop-develkdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel