Menu

#14 *** glibc detected *** python: free(): invalid pointer: 0xb7

open
nobody
None
5
2007-05-15
2007-05-15
P Adhia
No

Environment:
Ubuntu : Fiesty Fawn
Python 2.5.1c1 (release25-maint, Apr 12 2007, 21:00:25)
DB2 9.1.2

All python-DB2 program produce above error message. Here's a simple program to reproduce the error.

#! /usr/bin/env python

import DB2

con = DB2.connect('ANYDB', 'xxxxxx', 'xxxxxx')
csr = con.cursor()
csr.close()
con.close()

Discussion

  • Nobody/Anonymous

    Logged In: NO

    i have the same error

    here is the error:

    >> python test-db2.py
    ('Sanders', 'Mgr ')
    *** glibc detected *** python: free(): invalid pointer: 0xb7d36d40 ***

    and here the script test-db2.py:

    #!/usr/bin/env python
    import DB2
    conn = DB2.connect(dsn='sample', uid='db2inst1', pwd='susi')
    curs = conn.cursor()
    curs.execute('select name, job from staff')
    one_row = curs.fetchone()
    print one_row
    curs.close()
    conn.close()

    it appears to happen when the python shell exit's.

     
  • Peter Fuereder

    Peter Fuereder - 2007-05-21

    Logged In: YES
    user_id=1798331
    Originator: NO

    hello

    sorry, yesterday I was a little bit to fast. I forgot to include some plattform information and my name.

    Maschine: dual AMD Athlon(tm) MP 1800+
    Kernel: Linux 2.6.20-15-generic #2 SMP i686 GNU/Linux
    I also ran Ubuntu Fiesty Fawn
    and yesterday I tried it with Python 2.5.1 (latest version from repo)

    Today I compiled Python 2.4.3 and tried PyDB2 with it - and it works.
    It seems there is a python 2.5 problem, but I am not such an expert.

     
  • P Adhia

    P Adhia - 2007-06-19

    Logged In: YES
    user_id=1163018
    Originator: YES

    I successfully tried the workaround suggested on
    http://forums.gentoo.org/viewtopic-t-316912-highlight-\***+glibc+detected+***+free+invalid+pointer+0x1003e590+***.html

    Specifially, I have set MALLOC_CHECK_=0 env.

    From various forums it appears that, this may be caused by missing INCREF or an extra DECREF. Until, this bug is fixed, the above link gives a viable workaround.

     
  • Jon Thoroddsen

    Jon Thoroddsen - 2008-02-14

    Logged In: YES
    user_id=2003727
    Originator: NO

    With such an easy reproduction, this is probably the PyObject_Del bug.
    Try the latest release, and see if it fixes it.

    "nobody" however might have incref/decref bug.

    Is there somebody out there who has this with releases 1.1.0-2 and 1.1.0-3 but
    for which it is fixed in 1.1.1 ?

     

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.