Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*xfsprogs\:\s+to\s+\-DDEBUG\s+or\s+not\s+to\s+\-DDEBUG\?\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*xfsprogs\:\s+to\s+\-DDEBUG\s+or\s+not\s+to\s+\-DDEBUG\?\s*$/: 3 ]

Total 3 documents matching your query.

1. xfsprogs: to -DDEBUG or not to -DDEBUG? (score: 1): Author: Eric Sandeen <sandeen@xxxxxxxxxxx>; Date: Thu, 04 Feb 2010 10:53:23 -0600; Fedora, long ago, disabled debug in the xfsprogs specfile: http://cvs.fedoraproject.org/viewvc/F-12/xfsprogs/xfsprogs.spec?r1=1.5&r2=1.6 * Wed Apr 20 2005 Dave Jones <davej@xxxxxxxxxx> - Disable debu; /archives/xfs/2010-02/msg00076.html (7,313 bytes)
2. Re: xfsprogs: to -DDEBUG or not to -DDEBUG? (score: 1): Author: Dave Chinner <david@xxxxxxxxxxxxx>; Date: Fri, 5 Feb 2010 13:31:34 +1100; Personally I'd prefer the repair process to stop if it comes across inconsistencies it can't handle. Ignoring them is as likely to "fix" the crash as it is to corrupt the filesystem more. On top of t; /archives/xfs/2010-02/msg00087.html (9,131 bytes)
3. Re: xfsprogs: to -DDEBUG or not to -DDEBUG? (score: 1): Author: Eric Sandeen <sandeen@xxxxxxxxxxx>; Date: Fri, 05 Feb 2010 15:14:56 -0600; Hrm. Well, that makes sense. OTOH, Debian turns it off too: $ grep DEBUG debian/rules options = export DEBUG=-DNDEBUG DISTRIBUTION=debian \ and for some reason when I take this out of the Fedora spec; /archives/xfs/2010-02/msg00103.html (10,414 bytes)

Current List: 1 - 3
Page: [1]