All of lore.kernel.org
 help / color / mirror / Atom feed
From: Girish Shilamkar <Girish.Shilamkar@Sun.COM>
To: tytso@mit.edu
Cc: Ext4 <linux-ext4@vger.kernel.org>, adilger@Sun.COM
Subject: Re: e2fsprogs segfaults during make check
Date: Mon, 08 Feb 2010 19:50:17 +0530	[thread overview]
Message-ID: <1265638817.3882.31.camel@metis> (raw)
In-Reply-To: <20100208121619.GF4494@thunk.org>

On Mon, 2010-02-08 at 07:16 -0500, tytso@mit.edu wrote:
> Well, I run "make check" all the time during the course of my
> development, so it must be something unique with RHEL5.
That is the surprising part, no other distros had problem. Even
rhel5/i686 passes all the tests.

> #1) Does it show up if you just unpack a source tree, and do a
>  "configure; make; make check" run in RHEL 5?
No, it doesn't show up. Problem appears when it is configured with 
--enable-elf-shlibs !!

> #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.
Tried that before but there were no segfaults seen.

> #3) Try downloading:
> 
>     http://master.kernel.org/~tytso/e2fsprogs_1.41.10-rc1.tar.gz
> 
> ... and see if you can see the problem there.
The problem is not seen for this version. Any tentative dates for 1.41.10 release ?

Thanks,
Girish



  reply	other threads:[~2010-02-08 14:19 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
2010-02-08 14:20   ` Girish Shilamkar [this message]
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=1265638817.3882.31.camel@metis \
    --to=girish.shilamkar@sun.com \
    --cc=adilger@Sun.COM \
    --cc=linux-ext4@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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.