From: tytso@mit.edu
To: Girish Shilamkar <Girish.Shilamkar@Sun.COM>
Cc: Ext4 <linux-ext4@vger.kernel.org>, adilger@Sun.COM
Subject: Re: e2fsprogs segfaults during make check
Date: Mon, 8 Feb 2010 07:16:19 -0500 [thread overview]
Message-ID: <20100208121619.GF4494@thunk.org> (raw)
In-Reply-To: <1265614286.3882.16.camel@metis>
On Mon, Feb 08, 2010 at 01:01:26PM +0530, Girish Shilamkar wrote:
> Hello,
> I found a problem while creating e2fsprogs rpms. Few of the tests
> fail with segfault during make check. The tests are d_loaddump, f_dup4,
> f_imagic_fs and r_resize_inode. This failure is only seen on rhel5,
> x86_64.
> On further searching I found that this error can reproduced when
> e2fsprogs is configured with shared elf libraries. For example,
> configure --enable-elf-shlibs, make; make check
> And this problem is seen from 1.41.7 version onwards.
>
> Any ideas/comments ?
Well, I run "make check" all the time during the course of my
development, so it must be something unique with RHEL5.
#1) Does it show up if you just unpack a source tree, and do a
"configure; make; make check" run in RHEL 5?
#2) In the build directory, cd to tests, and then run the command:
(. $(srcdir)/tests/test_config; debugfs)
.. and see if you get a core dump. (Replace $(srcdir) with the top
level source tree directory. If you are building in the source tree,
you can just do "(. test_config ; debugfs)"; if you are building with
the build directory located in a "build" subdirectory under the source
tree, you could do "(. ../tests/test_config ; debugfs)", etc.
If you do get a core dump, run it under gdb and get a stack trace,
and/or see if anything is showing up in stderr that might be help
explain what's going on.
#3) Try downloading:
http://master.kernel.org/~tytso/e2fsprogs_1.41.10-rc1.tar.gz
... and see if you can see the problem there.
Thanks,
- Ted
next prev parent reply other threads:[~2010-02-08 12:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-08 7:31 e2fsprogs segfaults during make check Girish Shilamkar
2010-02-08 12:16 ` tytso [this message]
2010-02-08 14:20 ` Girish Shilamkar
2010-02-08 14:28 ` tytso
2010-02-08 15:57 ` Eric Sandeen
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=20100208121619.GF4494@thunk.org \
--to=tytso@mit.edu \
--cc=Girish.Shilamkar@Sun.COM \
--cc=adilger@Sun.COM \
--cc=linux-ext4@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).