From: Eric Sandeen <sandeen@sandeen.net>
To: Bartosz Cisek <bartosz.cisek@nasza-klasa.pl>
Cc: Christoph Hellwig <hch@infradead.org>,
Michael Monnerie <michael.monnerie@is.it-management.at>,
xfs@oss.sgi.com
Subject: Re: xfs_repair segfaut in stage 6
Date: Wed, 14 Sep 2011 10:23:36 -0500 [thread overview]
Message-ID: <4E70C6F8.3020906@sandeen.net> (raw)
In-Reply-To: <4E70C3CA.7010103@nasza-klasa.pl>
On 9/14/11 10:10 AM, Bartosz Cisek wrote:
> W dniu 14.09.2011 16:57, Eric Sandeen pisze:
>> If it worked for Christoph and not for Bartosz ....
>>
>> Is the -DDEBUG / -DNDEBUG type setting the same in both cases?
>> Maybe Fedora is the only one doing -DNDEBUG :( but maybe worth
>> checking.
>
> Tested both. I was wodering why I got 'value optimized out' in gdb, so
> compiled with DEBUG=-DNDBEUG and DEBUG=-DDEBUG. Both crashed, both had
> 'optimized out' values in gdb backtrace.
>
> I found two placed where DEBUG may be overwritten:
>
> hd-slave5 ~/devel/xfsprogs # ack-grep NDEBUG
> libxfs/Makefile
> 39:DEBUG = -DNDEBUG
>
> libxlog/Makefile
> 16:DEBUG = -DNDEBUG
>
> When I changed -DNDEBUG to -DDEBUG/ compilation failed.
yeah, that's why it's overridden in those places. :)
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-09-14 15:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-09 8:43 xfs_repair segfaut in stage 6 Bartosz Cisek
2011-09-09 12:01 ` Michael Monnerie
2011-09-09 15:06 ` Bartosz Cisek
2011-09-12 15:42 ` Bartosz Cisek
2011-09-12 15:58 ` Christoph Hellwig
2011-09-12 16:12 ` Christoph Hellwig
2011-09-14 9:38 ` Bartosz Cisek
2011-09-14 14:24 ` Christoph Hellwig
2011-09-14 14:57 ` Eric Sandeen
2011-09-14 15:10 ` Bartosz Cisek
2011-09-14 15:23 ` Eric Sandeen [this message]
2011-09-14 14:59 ` Bartosz Cisek
2011-09-14 15:38 ` Christoph Hellwig
2011-09-14 16:05 ` Bartosz Cisek
2011-09-20 20:25 ` Alex Elder
2011-09-20 20:28 ` Christoph Hellwig
2011-09-09 12:38 ` Christoph Hellwig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E70C6F8.3020906@sandeen.net \
--to=sandeen@sandeen.net \
--cc=bartosz.cisek@nasza-klasa.pl \
--cc=hch@infradead.org \
--cc=michael.monnerie@is.it-management.at \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.