Purify & Python - problems

[Randall Hopper]

   > python
   Segmentation fault (core dumped)

It fails right away, core dumping while doing a legitimate sprintf.
Anyone hit this before?

-- 
Randall Hopper
aa8vb at yahoo.com


****  Purify instrumented python-o32-g-purify (pid 974871)  ****
ABR: Array bounds read:
  * This is occurring while in:
        _doprnt+0x110448     [doprnt.c:417]
        sprintf+0x10f960     [sprintf.c:31]
        Py_GetBuildInfo+0x37ac48 [getbuildinfo.c:34]
        Py_GetVersion+0x2c2038 [getversion.c:42]
        _PySys_Init+0x2cf094 [sysmodule.c:401]
        Py_Initialize+0x261c5c [pythonrun.c:142]
        Py_Main+0x22706c     [main.c:245]
        main+0x2261e0        [python.c:12]
        __istart+0x2261ec    [crt1tinit.s]
  * Reading 4 bytes from 0x51e1898 between the a.out's text section and the data
.

****  Purify instrumented python-o32-g-purify (pid 974871)  ****
COR: Fatal core dump:
  * This is occurring while in:
        _doprnt+0x110448     [doprnt.c:417]
        sprintf+0x10f960     [sprintf.c:31]
        Py_GetBuildInfo+0x37ac48 [getbuildinfo.c:34]
        Py_GetVersion+0x2c2038 [getversion.c:42]
        _PySys_Init+0x2cf094 [sysmodule.c:401]
        Py_Initialize+0x261c5c [pythonrun.c:142]
        Py_Main+0x22706c     [main.c:245]
        main+0x2261e0        [python.c:12]
        __istart+0x2261ec    [crt1tinit.s]
  * Received signal 11 (SIGSEGV - Segmentation fault)
  * Handler function: SIG_DFL
  * Faulting address = 0x4b2f6e8
  * Signal mask: (SIGSEGV) 
  * Pending signals: