[Bug 798137] Re: bibtool crashed with SIGSEGV in __libc_start_main()

2012-01-09 Thread cboettig
I get this error as well. Perhaps this is related to the static memory allocation? I seem to get this error with large bibfiles (e.g. ~1000 entries with abstracts) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 798137] Re: bibtool crashed with SIGSEGV in __libc_start_main()

2011-10-21 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: bibtool (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/798137 Title:

[Bug 798137] Re: bibtool crashed with SIGSEGV in __libc_start_main()

2011-10-21 Thread J C Nash
I get a segfault on an Asus UL30A laptop (Genuine Intel(R) CPU U7300) which is 64bit and running Ubuntu Lucid 10.04 (updated to .2) but not under same OS on AMD Phenom II X6 1090T. Tried purging and reinstalling bibtool. Suggestions for test cases welcome. JN -- You received this bug

[Bug 798137] Re: bibtool crashed with SIGSEGV in __libc_start_main()

2011-10-21 Thread J C Nash
Further to above, I decided to get source (now version 2.53 while repository has 2.51) and built it. This did NOT give the segfault. JN -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/798137 Title:

[Bug 798137] Re: bibtool crashed with SIGSEGV in __libc_start_main()

2011-06-16 Thread Michael Schmidt
** Attachment added: bibtex file https://bugs.launchpad.net/bugs/798137/+attachment/2171288/+files/semi-direct_product.bib ** Visibility changed to: Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.