https://bugs.freedesktop.org/show_bug.cgi?id=73073

          Priority: medium
            Bug ID: 73073
          Assignee: libreoffice-bugs@lists.freedesktop.org
           Summary: exception from evaluateStatusVector
                    (firebird/Util.cxx:53) after SQL error
          Severity: normal
    Classification: Unclassified
                OS: All
          Reporter: lo_b...@iseries-guru.com
          Hardware: Other
            Status: NEW
           Version: 4.3.0.0.alpha0+ Master
         Component: Database
           Product: LibreOffice

Steps to reproduce:

(1) Run LibreOffice with command-line parameter --base to create (but
    do not register) /tmp/a1.odb with embedded firebird database.
    Program presents window "a1.odb".

(2) Take menu options Tools > "SQL...".  Program presents window
    "Execute SQL Statement".

(3) Paste command 
        create table t1 ( id integer not null, field1 varchar(20) not
        null );
    into "Command to Execute" and click <Execute>.  LO reports status:
    "1: Command executed successfully."

(4) Paste command
        CREATE TRIGGER T1_BI FOR T1
        ACTIVE BEFORE INSERT POSITION 0
        AS BEGIN
        if (new.id IS null) THEN new.id =
        GEN_ID(GEN_T1ID, 1);
        END
    into "Command to execute" and click <Execute>.  LO reports status:
        2: firebird_sdbc error:
        *invalid request BLR at offset 23
        *generator GEN_T1ID is not defined
        caused by
        'isc_commit_transaction'
    This is entirely to be expected.  (It was an accident the first
    time I did it.)

(5) Close window "Execute SQL Statement".  Program returns focus to
    window "a1.odb".

(6) Take menu options File > Quit.  Program presents prompt "Save
    Document?".

(7) Click <Save>.  Program fails with SIGABRT; the .odb is not
    updated.


Note that the failure is somewhat fragile:

(*) Not every SQL error in place of step (4) is followed by a crash.
    On the other hand, I have seen failures even when step (4) was
    followed by perfectly good SQL commands.

(*) I am using a debug build.  Unless the problem is seen in a
    non-debug build, I would presume that the debug build is part of
    the cause of the crash.


These observations are from master commit b0926378, fetched
2013-12-06, configured as:

    --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 executing on debian-wheezy:

    $ uname -a
    Linux debian 3.2.0-4-amd64 #1 SMP Debian 3.2.51-1 x86_64 GNU/Linux

    $ java -version
    java version "1.6.0_27"
    OpenJDK Runtime Environment (IcedTea6 1.12.6) (6b27-1.12.6-1~deb7u1)
    OpenJDK 64-Bit Server VM (build 20.0-b12, mixed mode)

    $ gcc --version
    gcc (Debian 4.7.2-5) 4.7.2
    Copyright (C) 2012 Free Software Foundation, Inc.
    This is free software; see the source for copying conditions.  There is NO
    warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

-- 
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

Reply via email to