Menu

#2 btree.c:3661:2: *** Internal Bug at constraintGeneration.c:1

v3.1.3
closed-fixed
nobody
None
5
2010-07-24
2007-11-23
Sami Farin
No

with sqlite-3.5.2, file src/btree.c, I get this:

( many files are needed, which I do not attach here.
http://www.sqlite.org/sqlite-3.5.2.tar.gz )

$ splint btree.c
Splint 3.1.2 --- 08 Nov 2007

btree.c:3661:2: *** Internal Bug at constraintGeneration.c:1441:
Unsupported preop in +1 [errno: 25]
*** Please report bug to splint-bug@splint.org ***
(attempting to continue, results may be incorrect)
btree.c:3661:2: *** Internal Bug at constraintGeneration.c:1442:
constraintGeneration.c:1442: llassert failed: FALSE:
Reached dead code! [errno: 25]
*** Please report bug to splint-bug@splint.org ***
(attempting to continue, results may be incorrect)

Discussion

  • Y Giridhar Appaji Nag

    Logged In: YES
    user_id=73891
    Originator: NO

    A simple test case to reproduce this bug is:

    $ cat test.c
    int main()
    {
    return +1;
    }

    From http://bugs.debian.org/462375
    Thanks "Bernhard R. Link" <brlink@debian.org>

     
  • Larry Yang

    Larry Yang - 2009-03-25

    I received a similar error message when I upgraded my splint version from 3.1.1 to 3.1.2.

    I verified that this error doesn't appear when using splint v3.1.1 using the test code from user "yganag".

     
  • Bill Pringlemeir

    I think I have fixed this in the most recent version of splint (from CVS). contraintGeneration.c v1.73. Thans to yganag for the simple test case.

     
  • Bill Pringlemeir

    • status: open --> pending
     
  • Bill Pringlemeir

    • status: pending --> pending-fixed
     
  • Bill Pringlemeir

    • milestone: --> v3.1.3
     
  • SourceForge Robot

    • status: pending-fixed --> closed-fixed
     
  • SourceForge Robot

    This Tracker item was closed automatically by the system. It was
    previously set to a Pending status, and the original submitter
    did not respond within 14 days (the time period specified by
    the administrator of this Tracker).

     

Log in to post a comment.

MongoDB Logo MongoDB