[Bug 705133] New: Review Request: btparser - Parser and analyzer for backtraces produced by GDB

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.

Summary: Review Request: btparser -  Parser and analyzer for backtraces produced by GDB

https://bugzilla.redhat.com/show_bug.cgi?id=705133

           Summary: Review Request: btparser -  Parser and analyzer for
                    backtraces produced by GDB
           Product: Fedora
           Version: rawhide
          Platform: All
        OS/Version: Linux
            Status: NEW
          Severity: medium
          Priority: medium
         Component: Package Review
        AssignedTo: nobody@xxxxxxxxxxxxxxxxx
        ReportedBy: kklic@xxxxxxxxxx
         QAContact: extras-qa@xxxxxxxxxxxxxxxxx
                CC: notting@xxxxxxxxxx, fedora-package-review@xxxxxxxxxx
   Estimated Hours: 0.0
    Classification: Fedora
      Story Points: ---


Spec URL: http://kklic.fedorapeople.org/btparser.spec
SRPM URL: http://kklic.fedorapeople.org/btparser-0.13-1.fc14.src.rpm
Description:
Btparser is a backtrace parser and analyzer, which works with
backtraces produced by the GNU Project Debugger. It can parse a text
file with a backtrace to a tree of C structures, allowing to analyze
the threads and frames of the backtrace and work with them.

Btparser also contains some backtrace manipulation and extraction
routines:
- it can find a frame in the crash-time backtrace where the program
  most likely crashed (a chance is that the function described in that
  frame is buggy)
- it can produce a duplication hash of the backtrace, which helps to
  discover that two crash-time backtraces are duplicates, triggered by
  the same flaw of the code
- it can "rate" the backtrace quality, which depends on the number of
  frames with and without the function name known (missing function
  name is caused by missing debugging symbols)

$ rpmlint btparser-0.13-1.fc14.src.rpm
btparser.src: W: spelling-error Summary(en_US) Backtrace -> Backtrack, Back
trace, Back-trace
btparser.src: W: spelling-error Summary(en_US) backtraces -> backtracks, back
traces, back-traces
btparser.src: W: spelling-error %description -l en_US backtrace -> backtrack,
back trace, back-trace
btparser.src: W: spelling-error %description -l en_US backtraces -> backtracks,
back traces, back-traces
1 packages and 0 specfiles checked; 0 errors, 4 warnings.

-> Backtrace is a commonly used word. The word is used in the GDB and glibc
manuals, and it is present in dictionaries.

$ rpmlint btparser-0.13-1.fc14.i386.rpm
btparser.i386: W: spelling-error Summary(en_US) Backtrace -> Backtrack, Back
trace, Back-trace
btparser.i386: W: spelling-error Summary(en_US) backtraces -> backtracks, back
traces, back-traces
btparser.i386: W: spelling-error %description -l en_US backtrace -> backtrack,
back trace, back-trace
btparser.i386: W: spelling-error %description -l en_US backtraces ->
backtracks, back traces, back-traces
btparser.i386: W: shared-lib-calls-exit /usr/lib/libbtparser.so.2.2.2
exit@xxxxxxxxx
1 packages and 0 specfiles checked; 0 errors, 5 warnings.

-> The shared library calls function exit only when malloc fails because of
some serious programming error.

$ rpmlint btparser-debuginfo-0.13-1.fc14.i386.rpm
1 packages and 0 specfiles checked; 0 errors, 0 warnings.

$ rpmlint btparser-devel-0.13-1.fc14.i386.rpm
btparser-devel.i386: W: no-documentation
1 packages and 0 specfiles checked; 0 errors, 1 warnings.

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
_______________________________________________
package-review mailing list
package-review@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/package-review


[Index of Archives]     [Fedora Legacy]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [KDE Users]     [Fedora Tools]