STR (0) Ensure that you have enabled experimental features. ( Tools > Options > LibreOfficeDev > Advanced > "Optional (unstable) options" > "Enable experimental features". If that was not already selected, restart LibreOffice. ) (1) From Welcome Center, click "Base Database". Program presents "Database Wizard" step 1 "Select Database". (2) Observe that radio button "Create a new database" is selected. (3) In dropdown list "Embedded Database" select "Firebird Embedded", and click <Next>. Program presents "Database Wizard" step 2 "Save and Proceed". (5) Observe that "Open the database for editing" is selected and "Create tables using the table wizard" is not selected. (6) Select "No, do not register the database" and click <Finish>. Program presents dialog Save. (7) Enter the pathname less ".odb" of a not-existing file. Program segfaults, leaving the named file with a size of 1751 bytes. This observation is from commit 48eccfb, fetched 2014-05-15 00:50 UTC, configured: --enable-option-checking=fatal --enable-dbgutil --enable-crashdump --without-system-postgresql --without-myspell-dicts --with-extra-buildid --without-doxygen --with-external-tar=/home/terry/lo_hacking/git/src built and running on debian-wheezy 64-bit. Note well, for comparison, that I do not see the problem in commit 49dff05, fetched 2014-05-12 14:59 UTC. This bug is less important than bug 78813 "Java core dump, segfault, when creating table", because this one happens with an experimental feature. However, a fix to this on may help that other by localizing it to HSQLDB or by enabling a backtrace not mangled by the JRE. So, I am setting this bug to block the other, but do not take it too seriously.
Created attachment 99231 [details] terminal output
Created attachment 99232 [details] gdb with backtrace from the segfault
Terrence: could you give a try to a newer version (> http://cgit.freedesktop.org/libreoffice/core/commit/?id=45e8fd5fcc71219d7564b475a3fec3d4536f70aa, see comment of this commit)?
With a debug build of commit 20c5618, fetched 2014-05-18 20:13 UTC, the segfault is gone. Thank you, Julien, for the heads-up. But that commit referenced fdo#41295, "MAILMERGE Corrupted PDFs in massmailing". Is that what you intended? If so, the resolution should be FIXED.
Thank you Terrence for your feedback, great it works now! :-) You're right it's better "FIXED"