All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Snitzer <snitzer@redhat.com>
To: lvm-devel@redhat.com
Subject: testsuite: get stacktrace if test drops core
Date: Wed, 17 Mar 2010 10:30:53 -0400	[thread overview]
Message-ID: <20100317143053.GA3836@redhat.com> (raw)
In-Reply-To: <87vdcv8do7.fsf@twilight.int.mornfall.net.>

On Wed, Mar 17 2010 at  6:07am -0400,
Petr Rockai <prockai@redhat.com> wrote:

> Hi,
> 
> Mike Snitzer <snitzer@redhat.com> writes:
> > Requires lvm be built with debugging (-g).
> > Also requires ulimit -c be non-zero (to drop core file).
> >
> > diff --git a/test/test-utils.sh b/test/test-utils.sh
> > index 6606c56..06b9636 100644
> > --- a/test/test-utils.sh
> > +++ b/test/test-utils.sh
> > @@ -24,6 +24,21 @@ STACKTRACE() {
> >  		echo "$i ${FUNC}() called from ${BASH_SOURCE[$i]}:${BASH_LINENO[$i]}"
> >  		i=$(($i + 1));
> >  	done
> > +
> > +	# Attempt to get a stacktrace if a core file exists
> > +	# and the lvm binary was built with debugging
> > +	TEST_LVM_BINARY=$(dirname $(which lvm))/../../tools/lvm
> > +	TEST_LVM_CORE=`ls core* | head -1`
> > +	GDB_BINARY=`which gdb`
> > +	READELF_BINARY=`which readelf`
> > +	if [ -n "$TEST_LVM_CORE" -a -n "$GDB_BINARY" -a -n "$READELF_BINARY" ]; then
> > +		if $READELF_BINARY -S $TEST_LVM_BINARY 2>&1 | grep -q .debug_info; then
> > +			echo bt > gdb_commands.txt
> > +			echo l >> gdb_commands.txt
> > +			echo quit >> gdb_commands.txt
> > +			$GDB_BINARY -batch -c $TEST_LVM_CORE -x gdb_commands.txt $TEST_LVM_BINARY
> > +		fi
> > +	fi
> >  }
> >  
> >  init_udev_transaction() {
> Looks good to me. Maybe change "bt" to "bt full"? That would also list
> local variables on the stack, so more useful data.

OK, I'll use "bt full".

> (Maybe even make it "thread apply all bt full", although we don't
> currently use threads here and we don't handle dmeventd coredumps
> either... maybe later.)

Right, we can always change it as needed.

> Otherwise, ACK.

Thanks,
Mike



      reply	other threads:[~2010-03-17 14:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-16 20:44 [PATCH] testsuite: get stacktrace if test drops core Mike Snitzer
2010-03-16 21:22 ` Mike Snitzer
2010-03-17 10:07 ` [PATCH] " Petr Rockai
2010-03-17 14:30   ` Mike Snitzer [this message]

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=20100317143053.GA3836@redhat.com \
    --to=snitzer@redhat.com \
    --cc=lvm-devel@redhat.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.