[ros-bugs] [Bug 4342] log2lines: Enhanced raddr2line replacement
ReactOS.Bugzilla at reactos.org
ReactOS.Bugzilla at reactos.org
Sun Dec 20 10:11:05 CET 2009
http://www.reactos.org/bugzilla/show_bug.cgi?id=4342
--- Comment #38 from jansssens <jroeloffzen at hotmail.com> 2009-12-20 10:11:04 CET ---
Created an attachment (id=4536)
--> (http://www.reactos.org/bugzilla/attachment.cgi?id=4536)
Version 1.9
The new -R update and regscan options are somewhat experimental. E.g. update is
not yet complete and regscan is depending on -S. But otherwise they seem to
work well.
Tested on Windows, builds on Linux.
Fixed some warnings for Linux build.
-R <cmd>
- update:
Updates the SVN log file. Currently only generates the index file
The SVN log file itself must be generated by hand in the sources
directory like this (-v is mandatory here):
svn log -v > svndb.log ('svn log' accepts also a range)
'svndb.log' and its index are needed for '-R regscan'
- regscan[,<range>]:
Scan for regression candidates. Essentially it tries to find
matches between the SVN log entries and the sources hit by
the backtrace.
<range> is the amount of revisions to look back from the build
revision (default 500)
The output of '-R regscan' is printed after EOF. The 'Changed path'
lists will contain only matched files.
Limitations:
- The bug should really be a regression.
- Expect a number of false positives.
- The offending change must be in the sources hit by the backtrace.
This mostly excludes changes in headerfiles for example.
- Must be combined with -S.
--
Configure bugmail: http://www.reactos.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
More information about the Ros-bugs
mailing list