[Bug 221873] Review Request: cgdb - A curses-based interface to the GNU Debugger (GDB)

[bugzilla at redhat.com]

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

Summary: Review Request: cgdb - A curses-based interface to the GNU Debugger (GDB)


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





------- Additional Comments From mtasaka at ioa.s.u-tokyo.ac.jp  2007-01-11 11:54 EST -------
Well,

* Documentation
  - Consider to add doc/htdocs

* File entry
  - From mockbuild log:
----------------------------------------------
warning: File listed twice: /usr/share/cgdb/cgdb.txt
----------------------------------------------

* Timestamp
  - This package includes a documentation
    ( /usr/share/cgdb/cgdb.txt ) and keeping timestamp
    on this file is preferable.
    Use:
----------------------------------------------
make install DESTDIR=$RPM_BUILD_ROOT INSTALL="%{__install} -c -p"
----------------------------------------------

* Some notes:
  - Please remove unnecessary comments like:
----------------------------------------------
#make %{?_smp_mflags}
#Let RPM strip the debug info.
#strip $RPM_BUILD_ROOT/%{_bindir}/cgdb
----------------------------------------------

* A question:
  - Why is the command prompt of cgdb is "tgdb"?

----------------------------------------------
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-redhat-linux-gnu"...Using host libthread_db
library "/lib/libthread_db.so.1".

(tgdb) 
----------------------------------------------

  And check my comment 8.

-- 
Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.