Hi Olly, I updated my local repo and built it again, but still getting the error. I took a look at python3/test-suite.log file, but I could not locate the source of test failure. Please find attached the log file with this email. I am available on IRC(nick : ankit_agrawal) if that seems a convenient medium for you to help me out with this issue. Thanks. Regards, Ankit Agrawal, Communication and Signal Processing, IIT Bombay. On Wed, Feb 26, 2014 at 6:04 PM, Olly Betts <olly at survex.com> wrote:> On Wed, Feb 26, 2014 at 10:29:01AM +0530, Ankit Agrawal wrote: > > I installed xapian smoothly as per the guidelines mentioned > in > > the HACKING file. However, I am getting test errors on tests related to > > python3 bindings after running them using `make check` on this fresh > > installation. The log can be seen here <http://pastebin.com/bnsTFG2e>. > Can > > anyone here help me out to figure out why they are failing? Please let me > > know if any more information is needed. Thank you. > > There was a segfault in the Python3 tests due to a bug in SWIG, > but that was resolved about a week ago. If you checked out your > source tree about that long ago, then I'd suggest you change directory > to the top level (inside only the xapian directory) and do: > > git pull > make > > That will fetch the latest version and rebuild anything that has > changed. > > Then you can run just the python3 tests with: > > cd xapian-bindings/python3 > make check > > If it's not that, then can you attach this log file from the tests: > > /home/ankit/foss/xapian/xapian/xapian-bindings/python3/test-suite.log > > Cheers, > Olly >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.xapian.org/pipermail/xapian-devel/attachments/20140226/6edabf6b/attachment-0002.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: test-suite.log Type: text/x-log Size: 1029 bytes Desc: not available URL: <http://lists.xapian.org/pipermail/xapian-devel/attachments/20140226/6edabf6b/attachment-0002.bin>
On Wed, Feb 26, 2014 at 08:20:00PM +0530, Ankit Agrawal wrote:> I updated my local repo and built it again, but still getting the > error. I took a look at python3/test-suite.log file, but I could not locate > the source of test failure. Please find attached the log file with this > email. I am available on IRC(nick : ankit_agrawal) if that seems a > convenient medium for you to help me out with this issue. Thanks.Hmm, the log isn't very informative. I'd suggest running the tests under the debugger, so that you can find out where the segfault happens. To do that, change to the python3 directory and use the run-python-test script. We set PYTHON3 to run python3 under gdb (I'm assuming "python3" is your Python3 interpreter - if not, you may need to change that): cd xapian-bindings/python3 PYTHON3='gdb --args python3' ./run-python-test smoketest.py You may need to install gdb (the GNU debugger) first - it'll probably be in a package called "gdb". You should get a "(gdb)" prompt - type "run" at that to actually run the program (it doesn't run right away to give you a chance to set breakpoints, watchpoints, etc, but we don't need to for this). When it segfaults, you should get back to the "(gdb)" prompt. Then "bt" should give you a backtrace showing where the crash happens (the lowest level functions come first, so are the most interesting). Cheers, Olly
Hi Olly, Thanks for the explicit and easy to follow instructions. This is the backtrace <http://pastebin.com/QDzBJxZ2> that I am getting and the source seems to be SWIG. Although highly unlikely(due to a recently solved SWIG ticket), I would just like to confirm whether this error is being replicated on other user's machines? Thanks. Regards, Ankit Agrawal, Communication and Signal Processing, IIT Bombay. On Thu, Feb 27, 2014 at 12:26 PM, Olly Betts <olly at survex.com> wrote:> On Wed, Feb 26, 2014 at 08:20:00PM +0530, Ankit Agrawal wrote: > > I updated my local repo and built it again, but still getting the > > error. I took a look at python3/test-suite.log file, but I could not > locate > > the source of test failure. Please find attached the log file with this > > email. I am available on IRC(nick : ankit_agrawal) if that seems a > > convenient medium for you to help me out with this issue. Thanks. > > Hmm, the log isn't very informative. > > I'd suggest running the tests under the debugger, so that you can find > out where the segfault happens. > > To do that, change to the python3 directory and use the run-python-test > script. We set PYTHON3 to run python3 under gdb (I'm assuming "python3" > is your Python3 interpreter - if not, you may need to change that): > > cd xapian-bindings/python3 > PYTHON3='gdb --args python3' ./run-python-test smoketest.py > > You may need to install gdb (the GNU debugger) first - it'll probably be > in a package called "gdb". > > You should get a "(gdb)" prompt - type "run" at that to actually run the > program (it doesn't run right away to give you a chance to set > breakpoints, watchpoints, etc, but we don't need to for this). > > When it segfaults, you should get back to the "(gdb)" prompt. Then > "bt" should give you a backtrace showing where the crash happens (the > lowest level functions come first, so are the most interesting). > > Cheers, > Olly >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.xapian.org/pipermail/xapian-devel/attachments/20140227/dd6a96d8/attachment-0002.html>