Core dump with 2.0.3rc7 + -CURRENT

[Adam K Kirchhoff]

Adam K Kirchhoff wrote:
>
> Hello all,
>
>    I have two separate machines running 7.0-CURRENT: a dual Xeon and
> an Athlon XP laptop.  I've grabbed the 2.0.3rc7 openoffice build (for
> 6.1-RELEASE) and installed it on both machines. It works great on the
> dual Xeon, but segfaults on the laptop.  After the core dump, I have
> two core files left in my home directory: javaldx.core and
> soffice.bin.core.  It sounds much like
> http://www.monkey.org/freebsd/archive/freebsd-ports-bugs/200412/msg00862.html,
> but with a much newer version of openoffice.
>
>    Out of curiousity, I tried running soffice.bin directly through gdb
> (after setting the LD_LIBRARY_PATH variable to
> /usr/local/openoffice.org-2.0.3rc7/program).  This is what I get:
>
> [ adamk at scroll - /usr/local/openoffice.org-2.0.3rc7/program ]: gdb
> ./soffice.bin
> GNU gdb 6.1.1 [FreeBSD]
> Copyright 2004 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and
> you are
> welcome to change it and/or distribute copies of it under certain
> conditions.
> Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB.  Type "show warranty" for
> details.
> This GDB was configured as "i386-marcel-freebsd"...(no debugging
> symbols found)...
> (gdb) run
> Starting program: /usr/local/openoffice.org-2.0.3rc7/program/soffice.bin
> (no debugging symbols found)...(no debugging symbols found)...(no
> debugging symbols found)...(no debugging symbols found)...(no
> debugging symbols found)...(no debugging symbols found)...(no
> debugging symbols found)...(no debugging symbols found)...(no
> debugging symbols found)...(no debugging symbols found)...(no
> debugging symbols found)...(no debugging symbols found)...(no
> debugging symbols found)...(no debugging symbols found)...(no
> debugging symbols found)...(no debugging symbols found)...(no
> debugging symbols found)...warning: Unable to get location for thread
> creation breakpoint: generic error
> [New LWP 100096]
> (no debugging symbols found)...(no debugging symbols found)...(no
> debugging symbols found)...(no debugging symbols found)...(no
> debugging symbols found)...(no debugging symbols found)...(no
> debugging symbols found)...(no debugging symbols found)...(no
> debugging symbols found)...(no debugging symbols found)...(no
> debugging symbols found)...(no debugging symbols found)...(no
> debugging symbols found)...
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to LWP 100096]
> 0x28ff54a6 in pthread_setcancelstate () from /lib/libpthread.so.2
> (gdb) bt
> #0  0x28ff54a6 in pthread_setcancelstate () from /lib/libpthread.so.2
> #1  0x28fe6710 in pthread_create () from /lib/libpthread.so.2
> #2  0x28ff22de in pthread_join () from /lib/libpthread.so.2
> #3  0x28ff61e2 in pthread_testcancel () from /lib/libpthread.so.2
> #4  0x28ff7971 in __error () from /lib/libpthread.so.2
> #5  0x28fddc19 in ?? () from /lib/libpthread.so.2
> #6  0xbfbfe8b8 in ?? ()
> #7  0x280ab118 in ?? () from /libexec/ld-elf.so.1
> #8  0xbfbfe868 in ?? ()
> #9  0x2808b0d5 in _rtld_error () from /libexec/ld-elf.so.1
> #10 0x2808ea93 in _rtld () from /libexec/ld-elf.so.1
> #11 0x2808a8f2 in .rtld_start () from /libexec/ld-elf.so.1
>
> Any ideas on what's wrong?

So I upgraded my install of -CURRENT and gave it another shot, but I'm
getting the same results on the laptop but not the desktop box.  Is
there anyway I can debug this further?

Adam