[Bashdb-help] bashdb 4.3-0.9: test failure

[John P. <joh...@gm...>]

With the following system I am getting 1 test suite failure:

$ uname -v
Darwin Kernel Version 13.4.0: Sun Aug 17 19:50:11 PDT 2014; 
root:xnu-2422.115.4~1/RELEASE_X86_64

$ gcc --version
Configured with: --prefix=/Library/Developer/CommandLineTools/usr 
--with-gxx-include-dir=/usr/include/c++/4.2.1
Apple LLVM version 6.0 (clang-600.0.47) (based on LLVM 3.5svn)
Target: x86_64-apple-darwin13.4.0
Thread model: posix

$ bash --version
GNU bash, version 4.3.30(1)-release (x86_64-apple-darwin13.4.0)
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
<http://gnu.org/licenses/gpl.html>

This is free software; you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

$ bashdb --version
bashdb, release 4.3-0.9

$ cat ./bashdb-4.3-0.9-test-suite.log
=====================================================
    bashdb 4.3-0.9: test/integration/test-suite.log
=====================================================

# TOTAL: 40
# PASS:  35
# SKIP:  4
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

.. contents:: :depth: 2

SKIP: test-file-with-spaces
===========================

Skipping test due to autoconf problems

SKIP: test-interrupt
====================


FAIL: test-sig
==============

bash(43327,0x7fff750a6310) malloc: *** error for object 0x4000000000000: 
pointer being freed was not allocated
*** set a breakpoint in malloc_error_break to debug
/Users/jp/Downloads/bashdb-4.3-0.9/test/integration/check-common.sh: 
line 25: 43327 Abort trap: 6           $SH -- ${top_builddir}/bashdb 
$dbg_opts -x "$cmdfile" "$debugged_script" $ARGS
--- /tmp/sig-filtered.check	2014-10-28 08:54:25.000000000 +0200
+++ /tmp/sig-filtered.right	2014-10-28 08:54:25.000000000 +0200
@@ -55,3 +55,5 @@
  +continue
  $? is 0
  $? is 0
+Debugged program terminated normally. Use q to quit or R to restart.
++### Should have printed a stack trace above...

SKIP: test-file-with-spaces
===========================

Skipping test due to autoconf problems

SKIP: test-interrupt
====================

It doesn't seem to be affecting anything in my usage so far. Let me know 
if there is anything I can help with in resolving this if you deem it 
necessary.

Cheers
John